Errors
Use the HTTP status and response body to determine whether a request succeeded.
| Status | Meaning |
|---|---|
200 OK | Request succeeded. |
201 Created | A webhook was registered. |
202 Accepted | A booking or cancellation was accepted for asynchronous processing — poll the attempt, or use webhooks, for the final outcome. |
204 No Content | A webhook was deleted. |
400 Bad Request | The request body or parameters are invalid. |
401 Unauthorized | No credential was supplied, or it doesn't match a valid, enabled, non-revoked API key. |
403 Forbidden | Your API key is valid but not scoped for this endpoint. |
404 Not Found | The resource does not exist or does not belong to your tenant. |
429 Too Many Requests | You've exceeded your tenant's rate limit. Back off and retry — rate limits are tracked per tenant, not shared across agencies. |
A note on booking outcomes
A booking attempt can reach Failed after its create request returns 202 Accepted. This
is a business outcome, not an HTTP error, and no charge is made. See the booking flow guide.