Seat cap reached
type | https://docs.frem.sh/reference/api/errors/seat-cap-reached |
| HTTP status | 409 Conflict |
What it means
The request conflicts with the resource’s current state.
Example detail messages returned with this error:
- Your org has {seatsUsed} of {t.seat_cap} contracted seats in use. Buy more seats from the billing page before provisioning new users.
What to do
Buy more seats, or enable seat overage, in Org admin -> Billing, then retry. Deactivated users do not consume a seat; reactivating one does.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/seat-cap-reached",
"title": "Conflict",
"status": 409,
"detail": "..."
}Branch on type, not on title or detail - those are human-readable and may be reworded.