REST API
The raw HTTP surface, with a playground that sends real requests.
Every endpoint below is generated from the same contract the server implements,
so this reference cannot drift from the running API. Each page carries the
request and response schemas, examples in several languages, and a playground
that sends a real request against https://api.unseal.space/api.
The playground talks to production. Requests you send from it create real projects, spend real credit, and — on the domain endpoints — can spend real money. Use a key scoped to the least authority you need, and read Authentication first.
Before you start
- Auth. Send your key as the
x-api-keyheader. Paste it into the playground's auth field to try an endpoint. - Only what a key can reach. This reference lists exactly the procedures an API key is allowed to call. Anything managed from a browser session only — workspace and key administration — is deliberately absent.
- Async by default.
POSTendpoints that start work (messages, deployments, domain registration) return an id immediately with202. Poll the matching status endpoint until it reaches a terminal state.
If you are writing TypeScript, prefer the SDK — it wraps these same
endpoints with types, retries, and the wait() helpers.