organization_limit_reached

HTTP status: 422

What happenedCopy Anchor Link

You reached an organization creation cap. The message names the cap.

The owned-organization cap counts organizations you currently own. Transfer ownership before creating another. This response has no Retry-After header.

The 24-hour cap counts organizations you created in the last 24 hours. The message states the UTC time when the next creation is possible. Transferring ownership does not reset that count.

The status is 422, the same class as domain_not_verified and recipient_suppressed: the request is valid, and a business rule refuses it. 429 is reserved for the request rate and send caps. It includes Retry-After, and clients retry that response. An owned cap does not clear on a short timer. 403 is reserved for a credential without permission. 409 is reserved for a conflict with an existing resource.

How to fixCopy Anchor Link

For the owned cap, transfer an organization or wait until purge removes an owner membership after deletion. For the 24-hour cap, create the organization at or after the UTC time in the message.

Known limitsCopy Anchor Link

The owned count includes organizations whose deletion has been requested. Receiving an ownership transfer can leave you above the owned cap. The cap is checked when an organization is created.

Source: docs/errors/organization_limit_reached.md.