Issue Entitlement
Issue a new entitlement to a customer, granting them access to a specific feature. The feature must exist and belong to the same merchant as the customer.
Authorizations
API key authentication
Body
The customer to issue the entitlement to.
^cus_[a-zA-Z0-9]+$The feature to grant access to.
^feat_[a-zA-Z0-9]+$The template defining the entitlement type and configuration.
- Option 1
- Option 2
- Option 3
When the entitlement becomes active. Defaults to now.
When the entitlement expires. Null means no expiration.
Optional subscription ID to associate with this entitlement.
Additional metadata for the entitlement.
Response
Entitlement successfully issued. Returns the same shape as GET /v1/entitlements/{entitlementId} (a discriminated EntitlementDetail), so callers can read featureType, hasAccess, and metered balance/usage fields directly from the create response.
- Option 1
- Option 2
- Option 3
A specific entitlement. The response shape varies by featureType.
entitlement Unique identifier for the entitlement.
^ent_[a-zA-Z0-9]+$Unique identifier for a customer
^cus_[a-zA-Z0-9]+$The feature this entitlement grants access to.
^feat_[a-zA-Z0-9]+$The unique key identifying the feature.
The type of feature.
boolean Unique identifier for a product
^prod_[a-zA-Z0-9]+$The subscription this entitlement is associated with, if any.
Current status of the entitlement.
active, canceled, expired When the entitlement becomes active.
When the entitlement expires. Null means no expiration.
Whether the customer currently has active access to this entitlement.
Additional metadata for the entitlement.
Always null for boolean entitlements. Surfaced on every entitlement so clients can read config without first switching on featureType.