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_portal:write.
Successful result
A successful request returns 200. The response schema below defines the body your integration receives.
Authorizations
Customer session tokens are specific tokens that are used to authenticate customers on your organization. You can create those sessions programmatically using the Create Customer Session endpoint.
Body
Subscription ID. Required if neither order_id nor checkout_id is provided.
Order ID for one-time purchases. Required if subscription_id is not provided.
Email of the customer to assign the seat to
External customer ID for the seat assignment
Customer ID for the seat assignment
External member ID for the seat assignment. Can be used alone (lookup existing member) or with email (create/validate member).
Member ID for the seat assignment.
Additional metadata for the seat (max 10 keys, 1KB total)
If true, the seat will be immediately claimed without sending an invitation email. API-only feature.
Checkout ID. Resolves to the subscription or order produced by the checkout.
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