Errors¶

Errors are RFC 9457 problem details, served as application/problem+json:

{
  "type": "https://dashboard.breqwatr.cloud/problems/manager_required",
  "code": "manager_required",
  "title": "Owner or admin required",
  "status": 403,
  "detail": "Only an owner or admin of this organisation can see this.",
  "request_id": "6f1c2d9e-3b7a-4c58-9e21-0a4d7b1f8c36"
}

Field	Meaning
`code`	What went wrong. It's stable, so match on this
`status`	The HTTP status
`title`, `detail`	For people to read. They follow the language of the request, so never match on them
`type`	A URI naming the problem. Match on `code` instead
`request_id`	Quote this when you contact support

Some errors add more: validation_failed adds errors, and deletion_blocked adds blocker, count and region.

400: the request is wrong¶

`bad_request`¶

Bad request. A required parameter is missing, or the Idempotency-Key is too long. detail names the parameter.

`invalid_cursor`¶

Invalid cursor. The cursor isn't one this API issued. Pass next_cursor back exactly as it was returned. See Pagination.

`invalid_parameter`¶

Invalid parameter. A parameter doesn't have a valid value. detail names the parameter. Check its allowed values in the Reference.

`invalid_period`¶

Invalid period. year and month don't name a calendar month. Use values such as year=2026&month=9.

401: the key isn't accepted¶

`invalid_token`¶

Invalid API key. The key is missing, wrong or revoked, or its owner can no longer use it. Check the Authorization header, then create a new key if needed. See Authentication.

`token_expired`¶

API key expired. The key is past its expiry. Create a new key from your profile.

403: you aren't allowed¶

`billing_details_incomplete`¶

Billing details incomplete. Creating a project needs the organisation's billing details. Complete them in the portal, then retry.

`billing_setup_required`¶

Payment method required. The organisation needs a payment method. Add one in the portal, then retry.

`manager_required`¶

Owner or admin required. Only an owner or admin of the organisation can do this. Use a key belonging to an owner or admin. See Roles and access.

`org_suspended`¶

Organisation suspended. The organisation is suspended. The key itself is fine. Contact support. A new key won't help.

`owner_required`¶

Owner required. Only the organisation's owner can do this. Use a key belonging to the owner.

404: not found¶

`not_found`¶

Not found. It doesn't exist, you can't reach it, or the feature isn't available on this cloud. Check the id and the key's access. See Roles and access.

409: the current state prevents it¶

`account_unclaimed`¶

Account not set up. The person has an account that hasn't been set up, so an invitation can't reach them. Ask support to resend their set-password link.

`already_member`¶

Already a member. The person is already a member of the organisation. No invitation is needed.

`deletion_blocked`¶

Project still holds resources. Instances or volumes remain in the project. blocker, count and region say what's in the way. Delete them, then retry. See Background operations.

`idempotency_key_in_progress`¶

Request already in progress. A request with this Idempotency-Key is still running. Retry once it has finished. See Safe retries.

`invitation_pending`¶

Invitation already pending. This email already has a pending invitation. No new invitation is needed.

`last_owner`¶

Last owner. The organisation must keep an owner. Transfer ownership to another member first.

`not_editable`¶

Request cannot be changed. Only a quota increase request staff sent back for more information can be resubmitted. Read the request's status, and wait for its review if it's pending.

`not_member_role`¶

Not a member-role membership. Project access applies only to members, because owners and admins see every project. Change the person's role first if they should have limited access.

`own_membership`¶

Your own membership. You can't change or remove your own membership. Use another owner or admin's key.

`per_project_access_off`¶

Per-project access is off. Per-project access isn't on for this organisation, so every member sees every project. Turn it on in the organisation's settings first.

`project_not_ready`¶

Project not ready. The project is still being created. Wait until its default region is ready, then retry. See Background operations.

`trial_project_limit`¶

Trial project limit reached. The organisation is on a free trial and has reached its project limit. Add a payment method in the portal to create more.

422: the request can't be applied¶

`idempotency_key_reused`¶

Idempotency-Key reused. This key was already used for a different request. Use a new key for a new request. See Safe retries.

`validation_failed`¶

Validation failed. One or more fields aren't valid. errors lists each field and its message.

429: too many requests¶

`rate_limited`¶

Rate limited. You've gone over a rate limit. Wait for the seconds in Retry-After, then retry. See Rate limits.

500: something went wrong on our side¶

`internal_error`¶

Internal error. An unexpected error on our side. Retry later, and quote request_id if you contact support.

503: the cloud can't be reached¶

`cloud_unavailable`¶

Cloud unavailable. A region couldn't be checked, so nothing was changed. Wait for the seconds in Retry-After, then retry.

`quota_unavailable`¶

Quota unavailable. The region's quota couldn't be read just now. Wait for the seconds in Retry-After, then retry.

Errors¶

400: the request is wrong¶

bad_request¶

invalid_cursor¶

invalid_parameter¶

invalid_period¶

401: the key isn't accepted¶

invalid_token¶

token_expired¶

403: you aren't allowed¶

billing_details_incomplete¶

billing_setup_required¶

manager_required¶

org_suspended¶

owner_required¶

404: not found¶

not_found¶

409: the current state prevents it¶

account_unclaimed¶

already_member¶

deletion_blocked¶

idempotency_key_in_progress¶

invitation_pending¶

last_owner¶

not_editable¶

not_member_role¶

own_membership¶

per_project_access_off¶

project_not_ready¶

trial_project_limit¶