Skip to content

SeatAssignmentErrorReason

SeatAssignmentErrorReason = "invalid_request" | "unauthorized" | "forbidden" | "unknown_seat_type" | "unknown_dimension_value" | "request_failed"

Why a seat-type assignment was refused, derived from the HTTP status of POST /api/sdk/user-contexts:

  • invalid_request (400) — malformed body, e.g. an empty user id.
  • unauthorized (401) — missing or invalid credential.
  • forbidden (403) — the credential is not a server key. Only a server key may write a seat assignment (D-36).
  • unknown_seat_type (422) — the handle is not one of the tenant’s current seat types.
  • unknown_dimension_value (422, code UNKNOWN_DIMENSION_VALUE) — a builtinDimensions value passed alongside the seat is outside its dimension’s vocabulary (BL-0382).
  • request_failed — any other non-2xx status.