Assign Seat
Intent
Runs the assign seat action.
When to call it
Call this when your workflow reaches the point where it must assign seat.
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.
Authorizations
Body
Subscription Id: Subscription ID. Required if neither order_id nor checkout_id is provided.
Order Id: Order ID for one-time purchases. Required if subscription_id is not provided.
Email: Email of the customer to assign the seat to.
External Customer Id: External customer ID for the seat assignment.
Customer Id: Customer ID for the seat assignment.
External Member Id: External member ID for the seat assignment. Can be used alone (lookup existing member) or with email (create/validate member).
Member Id: Member ID for the seat assignment.
Metadata: Additional metadata for the seat (max 10 keys, 1KB total).
Immediate Claim: If true, the seat will be immediately claimed without sending an invitation email. API-only feature.
Response
Request completed successfully
The time Ruba created this record.
The time this record last changed.
Id: Seat ID.
Status: Status of the seat.
pending, claimed, revoked Subscription Id: Subscription ID (for recurring seats).
Order Id: Order ID (for one-time purchase seats).
Customer Id: Customer ID. When member_model_enabled is true, this is the billing customer (purchaser). When false, this is the seat member customer.
Member Id: Member ID of the seat occupant.
Member: Member associated with this seat.
Email: Email of the seat member (set when member_model_enabled is true).
Customer Email: Assigned customer email.
Invitation Token Expires At: When the invitation token expires.
Claimed At: When the seat was claimed.
Revoked At: When the seat was revoked.
Seat Metadata: Additional metadata for the seat.