POST · Domains
Hold a Snapback booking for human confirmation
Hold a Snapback booking for human confirmation
/api/v1/snapback/bookings
Description
Prices the booking and returns {status:"confirmation_required", confirmationUrl, …}. It books nothing and spends nothing — show the human the confirmationUrl; once they approve in the Inleed client area the booking is made and the prepaid balance is debited. The domain is only ever registered if the attempt succeeds at the drop.
Body
Send as application/json.
| Name | Type | Description |
|---|---|---|
domain
required
|
string |
The dropping domain to book, e.g. example.se.
|
contact_id
|
string |
Up to 64 characters. Pattern ^[A-Za-z0-9._-]+$.
|
billing_address_id
|
integer | Optional: settle against this billing profile instead of the primary one. It must be Swedish and at the standard VAT rate. Minimum 1. |
attempt_key
|
string | Idempotency key for this intent. Keep it stable across retries so a timed-out retry cannot buy the same thing twice. Up to 128 characters. |
Responses
A 200 response returns the shape shown in the rail.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.