domains
orc domains manages Domain resources used for brand verification and ingestion. List, inspect, create, update, or delete domains, start ownership checks, inspect status, and request rechecks. Filter lists by the primary or alternate role, verification state, or ingestion state.
Authentication and access to the target Workspace are required. The id is the Domain resource ID returned by listing, not a hostname. This is separate from a brand’s domain and domains registry. Check the saved verification method and token-publication instructions before starting verification.
Usage
orc domains list --workspace <workspace-id>Inspect Domain resources and verification status.
Subcommands
list
List non-deleted Domains. Combine --brand-id, --role, --verification-status, and --ingestion-status to filter results. Preserve filters while following cursors.
orc domains list [options]Unique options
--brand-id
Filter by brand id in the selected workspace. Omit to include domains or suggestions for all brands.
Type: string. Optional.
orc domains list --brand-id <value>--role
Filter by the stored domain role. Omit to include both primary and alternate domains.; enum: primary|alternate
Type: string. Optional.
orc domains list --role <value>--verification-status
Filter by the stored ownership verification state. Omit to include all states.; enum: unverified|pending|verified|failed
Type: string. Optional.
orc domains list --verification-status <value>--ingestion-status
Filter by the stored ingestion state. Omit to include all states.; enum: not_configured|configured|active|error
Type: string. Optional.
orc domains list --ingestion-status <value>create
domain and a brand_id in the current Workspace are required. Role defaults to alternate, and verification starts as unverified. Setting a verification method creates a token but does not start verification.
orc domains create [options]Unique options
--idempotency-key
Retry identity for operations that support idempotency. Use a unique key for each new operation, and reuse it only when retrying the same HTTP method, path, query values and exact request body. JSON whitespace changes can count as a different body. Keys contain 1–255 characters after trimming and expire after 24 hours. A completed JSON response is replayed without repeating the operation. A different request using the same key returns 409 idempotency_error. An in-progress request returns 409 idempotency_in_progress with Retry-After: 2. Whether this header is required depends on the operation.
Type: string. Optional.
orc domains create --idempotency-key <value>--domain
(required) Hostname stored for ownership verification and ingestion, without a protocol or path.
Type: string. Optional.
orc domains create --domain <value>--brand-id
(required) Existing non-deleted brand in the selected workspace to which this domain belongs.
Type: string. Optional.
orc domains create --brand-id <value>--role
Stored domain role: primary for the main domain, alternate for an additional domain. Defaults to alternate.; enum: primary|alternate
Type: string. Optional.
orc domains create --role <value>--verification-method
Ownership check method: dns_txt publishes the token in DNS; file_upload serves it at /.well-known/orchestor-domain-verify; manual requires support. Null means no method is configured. Omitted or null leaves the method unconfigured.; enum: |dns_txt|file_upload|manual; (use "null" or "reset" to clear)
Type: string. Optional.
orc domains create --verification-method <value>--ingestion-method
Configured traffic ingestion method. Null means no method is selected. Omitted or null leaves the method unconfigured.; enum: |log_forwarder|edge_worker|manual_upload; (use "null" or "reset" to clear)
Type: string. Optional.
orc domains create --ingestion-method <value>Examples
orc domains create --domain acme.example --brand-id <brand-id> --verification-method dns_txt --workspace <workspace-id>Register a Domain for DNS verification
get
Retrieve details by Domain ID. Use verification get for the token and instructions. Missing, deleted, or out-of-Workspace IDs return 404.
orc domains get <id> [options]update
Change only supplied role, verification_method, and ingestion_method. A non-null verification method regenerates the token and resets status to unverified, even if unchanged. Null clears the method but retains the stored token and state. Verification does not start.
orc domains update <id> [options]Unique options
--role
Stored domain role: primary for the main domain, alternate for an additional domain. Omit to keep the stored value.; enum: primary|alternate
Type: string. Optional.
orc domains update <id> --role <value>--verification-method
Ownership check method: dns_txt publishes the token in DNS; file_upload serves it at /.well-known/orchestor-domain-verify; manual requires support. Null means no method is configured. Omit to keep the stored value. A non-null value replaces the token and resets status to unverified. Null clears the method without clearing the existing token or status.; enum: |dns_txt|file_upload|manual; (use "null" or "reset" to clear)
Type: string. Optional.
orc domains update <id> --verification-method <value>--ingestion-method
Configured traffic ingestion method. Null means no method is selected. Omit to keep the stored value.; enum: |log_forwarder|edge_worker|manual_upload; (use "null" or "reset" to clear)
Type: string. Optional.
orc domains update <id> --ingestion-method <value>delete
Soft-delete a Domain and return id and deleted: true. Subsequent lists and reads exclude it. Missing or deleted IDs return 404.
orc domains delete <id> [options]verify
Start asynchronous ownership verification using the saved verification_method. An unset method returns 400. Status becomes pending, and attempts and previous errors are reset. Check status through the returned poll_url.
orc domains verify <id> [options]Unique options
--idempotency-key
Retry identity for operations that support idempotency. Use a unique key for each new operation, and reuse it only when retrying the same HTTP method, path, query values and exact request body. JSON whitespace changes can count as a different body. Keys contain 1–255 characters after trimming and expire after 24 hours. A completed JSON response is replayed without repeating the operation. A different request using the same key returns 409 idempotency_error. An in-progress request returns 409 idempotency_in_progress with Retry-After: 2. Whether this header is required depends on the operation.
Type: string. Optional.
orc domains verify <id> --idempotency-key <value>Examples
orc domains verify <domain-id> --workspace <workspace-id>Start verification after publishing the token
verification get
Retrieve saved status, token, and method-specific instructions. A verified Domain checked more than 24 hours ago may enqueue a background recheck. stale_recheck_enqueued indicates a request, not completion.
orc domains verification get <id> [options]Unique options
--idempotency-key
Retry identity for operations that support idempotency. Use a unique key for each new operation, and reuse it only when retrying the same HTTP method, path, query values and exact request body. JSON whitespace changes can count as a different body. Keys contain 1–255 characters after trimming and expire after 24 hours. A completed JSON response is replayed without repeating the operation. A different request using the same key returns 409 idempotency_error. An in-progress request returns 409 idempotency_in_progress with Retry-After: 2. Whether this header is required depends on the operation.
Type: string. Optional.
orc domains verification get <id> --idempotency-key <value>Examples
orc domains verification get <domain-id> --workspace <workspace-id> --jsonRetrieve the token and publication instructions
verification refresh
Request another ownership check with the configured method and published token. Return 202 and poll_url, with status set to pending. Check instructions first if the token needs to be republished.
orc domains verification refresh <id> [options]Unique options
--idempotency-key
Retry identity for operations that support idempotency. Use a unique key for each new operation, and reuse it only when retrying the same HTTP method, path, query values and exact request body. JSON whitespace changes can count as a different body. Keys contain 1–255 characters after trimming and expire after 24 hours. A completed JSON response is replayed without repeating the operation. A different request using the same key returns 409 idempotency_error. An in-progress request returns 409 idempotency_in_progress with Retry-After: 2. Whether this header is required depends on the operation.
Type: string. Optional.
orc domains verification refresh <id> --idempotency-key <value>verification recheck
Recheck domain verification
orc domains verification recheck <id> [options]Unique options
--idempotency-key
Retry identity for operations that support idempotency. Use a unique key for each new operation, and reuse it only when retrying the same HTTP method, path, query values and exact request body. JSON whitespace changes can count as a different body. Keys contain 1–255 characters after trimming and expire after 24 hours. A completed JSON response is replayed without repeating the operation. A different request using the same key returns 409 idempotency_error. An in-progress request returns 409 idempotency_in_progress with Retry-After: 2. Whether this header is required depends on the operation.
Type: string. Optional.
orc domains verification recheck <id> --idempotency-key <value>Ownership verification flow
- Set
verification_methodthroughcreateorupdate. Methods aredns_txt,file_upload, andmanual. - Publish DNS records or files following the token and instructions from
verification get. Manual verification requires support. - Run
verifyorverification refresh. Acceptance does not mean verification succeeded. - Poll
verification getand inspect theverifiedorfailedresult.
Passing a method to verify does not override saved settings. Change it with update --verification-method. Registration and verification settings alone do not guarantee active ingestion. Ingestion methods are log_forwarder, edge_worker, and manual_upload.
Permissions
Access to the target Workspace is required. Changes require the corresponding write permissions.
Global Options
The following global options can be used with orc domains:
For details and examples, see global options.