End Seat
Intent
Removes the seat.
When to call it
Call this only after your application has identified the seat that should be removed.
Access boundary
Authorize the request with a token that carries customer_seats:write.
Successful result
A successful request returns 200. The response schema below defines the body your integration receives.
Operational notes
Scopes: customer_seats:write
Authorizations
You can generate an Organization Access Token from your organization's settings.
Path Parameters
Response
Successful Response
The time Ruba created this record.
The time this record last changed.
The seat ID
Status of the seat
pending, claimed, revoked The subscription ID (for recurring seats)
The order ID (for one-time purchase seats)
The customer ID. When member_model_enabled is true, this is the billing customer (purchaser). When false, this is the seat member customer.
The member ID of the seat occupant
The member associated with this seat
Email of the seat member (set when member_model_enabled is true)
The assigned customer email
When the invitation token expires
When the seat was claimed
When the seat was revoked
Additional metadata for the seat