customer_id you send doesn’t already exist, Autumn will automatically
create a new customer. You can optionally set the properties of this new customer
through the customer_data field.Authorizations
Use your Autumn Secret Key as the Bearer token.
Body
ID which you provided when creating the customer
ID of the product to check access to. Required if feature_id is not provided.
ID of the feature to check access to. Required if product_id is not provided.
If you know the amount of the feature the end user is consuming in advance. If their balance is below this quantity, allowed will be false.
If true, a usage event will be recorded together with checking access. The required_balance field will be used as the usage value.
If true, the response will include a preview object, which can be used to display information such as a paywall or upgrade confirmation.
If using entity balances (eg, seats), the entity ID to check access for.
Additional customer properties. These will be used if the customer's properties are not already set.
Response
Whether the customer has access to the feature or product
Your unique identifier for the customer
ID of the feature being checked
Status code indicating the result of the check
Balances of the associated feature or credit system
Information about the feature, used to display information such as a paywall. Returned if check is called with a feature_id and with_preview is true.
Information about the product, used to display information such as an upgrade confirmation. Returned if check is called with a product_id and with_preview is true.

