List domains
List your custom domains with their verification status and DNS records.
Filter by project, app, or environment using IDs or slugs, or send {} to list
domains across your workspace.
Use any filter on its own or combine filters to narrow the results.
Results match all supplied filters. Omitting environment includes all matching environments.
Results include only domains you have permission to read, sorted by ID.
When hasMore is true, send the returned cursor to get the next page.
status: verified means the domain is verified. Unkey has configured routing and requested a
certificate. Each domain includes its full dnsRecords. Each record has a verified flag.
The flag shows which records Unkey has read back, so you can see which records are still
missing without a second call. Some providers hide a record from DNS lookups, for example a
proxied or flattened routing record. Such a record stays false while it serves traffic.
Required Permissions
Use a root key with the environment.*.read_domain permission.
A successful request returns an empty list if no matching domains are readable by your key.
Authorizations
Unkey uses bearer tokens for authentication. Public integrations use root keys, while the dashboard proxy uses short-lived JWTs. To authenticate, include the token in the Authorization header of each request:
Root keys have specific permissions attached to them, controlling what operations they can perform. Legacy permissions use tuple strings like api.*.create_key; resource permissions use Unkey Resource Names plus actions, like unkey:v1:ws_123:keyspaces/*#create_key.
Security best practices:
- Keep root keys secure and never expose them in client-side code
- Use different root keys for different environments
- Rotate keys periodically, especially after team member departures
- Create keys with minimal necessary permissions following least privilege principle
- Monitor key usage with audit logs.
Body
Filter domains within a workspace. All filters are optional and combine with AND. Each resource filter matches its ID or slug directly, even when its parent filters are omitted. A missing resource or a resource that does not match the other filters produces an empty list.
Response
Successfully retrieved the permitted domains that match every filter. Missing or mismatched filtered resources return an empty list.