Check whether a subscription checkout landed
POST/api/v1/billing/subscription/checkout/verify
Report a subscription checkout's state after the browser comes back.
This endpoint NEVER changes the plan. The webhook is the authority; this is what the success page polls until the webhook has landed.
- 403 when the checkout's metadata names another organization.
- Scope required:
billing:manage.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 429
- 500
Successful Response
Bad request — malformed input or failed validation.
Missing, expired, or invalid credentials.
Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.
Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).
Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).
Semantic validation failure — request shape was valid but contents were not.
Too many requests — rate limited. Retry after the window resets.
Internal server error — unexpected failure.