FAQ

What’s the difference between an Order and Mailboxes/buy?

POST /v1/api/orders registers a new domain and creates its mailboxes in one call — use it when starting from scratch. POST /v1/api/mailboxes/buy only creates mailboxes, on a domain you’ve already registered and verified in your workspace.

How do I get mailboxes into my sending tool without copying credentials by hand?

Sequencers: add a connection to your platform once (POST /v1/api/sequencers/add), then bulk-connect any set of mailboxes into it with POST /v1/api/sequencers/export. Poll /export/status (or use a webhook) to know when each mailbox is live in the tool.

Does one API key work across all my workspaces?

Yes — a key authenticates as your team. Which workspace a request applies to is selected per-request via the X-Workspace-Id header, not baked into the key. See Overview & Authentication.

Why does an endpoint that only reads data use POST?

Several list/filter endpoints (mailboxes/list, sequencers/list, infra-guard/alerts, …) take their filters in a JSON body rather than a query string, so they’re POST. Check each page’s method column rather than assuming.

My request returns 404 even though the resource clearly exists

Almost always a missing or wrong X-Workspace-Id header — the API returns 404/400 rather than leaking whether a resource exists in a workspace your key can’t see. Confirm the header first; see Errors & Rate Limits.

Is there a sandbox / test mode?

Not currently — build against real (small) domains/mailboxes in a dedicated test workspace, and use Orders / PreWarm status polling to confirm each step before scaling up a bulk operation.

Where do I ask something this page doesn’t answer?

Reach out through your Infrabox dashboard, or email support — the fastest way to get an accurate answer for anything account- or billing-specific.