Buy domains without inboxes
Register domains without ordering inboxes. Use this to build up your own
domain supply, then order inboxes on those domains later with
POST /orders.
The purchase is a normal order with no mailbox provider. It appears in
GET /orders, sends the order.in_progress and order.completed
webhooks (each webhook domain has provider: null), and completes once
every domain is registered. Each domain is charged its registration
price from your wallet now, and renews yearly from your wallet unless
you set auto_renew: false.
Each domain must be available and not premium, so check names with
POST /domains/availability first. One purchase can mix TLDs. Every
domain is bought or none is: an unavailable name or a name already in
an active order rejects the whole request without charging.
workspace_id is optional. Send it to assign the domains to that
workspace (and its customer); omit it to keep them in your organization
unassigned. A later POST /orders for the same workspace or customer
can use these domains.
Requires a live key with full permissions and an Idempotency-Key.
Repeating a request with the same key and body returns the same order
without charging again. Sandbox keys return 403 forbidden.
Authorizations
Headers
Required for order creation. Pool attach also supports this header for
durable retries. Workspace creation does not use it. The value is
unique across the Partner account.
Reuse it only with the same endpoint and unchanged request body. When
retrying an Instantly order after
422 provider_login_credentials_required, you may add or replace only
destination.login_credentials; every other field must stay unchanged.
For a Smartlead Microsoft order with that error, repair the
target through POST /workspaces, then retry the unchanged order with
the same key.
Retry 503 provider_unavailable or 500 internal_error with the same
key and unchanged body.
After pool attach returns 409 insufficient_inventory, wait for pool
inventory to be replenished, then retry the unchanged body with the
same key. After 422 provider_login_credentials_required or
422 provider_credentials_invalid, repair the target workspace, then
retry the unchanged body with the same key.
1 - 256