If the
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
application/json
ID of the feature to track usage for.
ID which you provided when creating the customer
How much usage should be deducted from the balance. Default is 1.
If using entity balances (eg, seats), the entity ID to track usage for.
An event name can be used in place of feature_id. This can be used if multiple features are tracked in the same event.
Unique identifier for the event. If the an event with the same key is sent multiple times, any subsequent events will be ignored and return an error.
Event properties that you can define.
Additional customer properties. These will be used if the customer's properties are not already set.

