Skip to main content

Bench seat cap reached

typehttps://docs.frem.sh/reference/api/errors/bench-seat-cap-reached
HTTP status409 Conflict

What it means

Every frembench seat your organisation has bought is already assigned to someone, so there is none left to give out. The detail names the cap.

This is about licences, not machines. It is raised when assigning a seat to a person — not when creating a bench, which is bench-cap-reached.

A seat stays assigned whether or not its holder has created a bench, because it is a licence to that named person. So a full seat list with idle holders is possible, and is worth reviewing before buying more.

What to do

Either revoke a seat from someone who no longer needs one:

curl -X DELETE \
  -H "Authorization: Bearer $FREMFORGE_TOKEN" \
  https://frem.sh/api/v1/orgs/<org>/frembench-seats/<login>

or raise the seat count in Billing → Benches. Raising it charges a prorated amount for the rest of the current term; revoking is free and takes effect immediately.

Revoking a seat does not delete the holder’s bench. It stops them creating a new one; the existing machine keeps running until it is reclaimed.

Response shape

All fremforge API errors are RFC 9457 problem+json:

{
  "type": "https://docs.frem.sh/reference/api/errors/bench-seat-cap-reached",
  "title": "Conflict",
  "status": 409,
  "detail": "..."
}

Branch on type, not on title or detail - those are human-readable and may be reworded.

Bench not foundBenches not enabled