When to Use
Use this as the primary entrypoint before billing operations so the customer record is always present and up to date. This endpoint is idempotent - calling it multiple times with the samecustomer_id will return the same customer without creating duplicates.
Request Body
Your unique identifier for the customer. Cannot contain
@, spaces, or periods. Only letters, numbers, underscores, and hyphens are allowed.Customer’s name.
Customer’s email address. Must be a valid email format.
Unique identifier (eg. serial number, device ID) to detect duplicate customers and prevent free trial abuse. Useful for identifying the same user across different accounts or devices.
Additional metadata for the customer. Can store any custom key-value pairs.
Stripe customer ID if you already have one. If provided, Autumn will link to your existing Stripe customer.
Whether to create the customer in Stripe. Defaults to
true if not specified.The ID of a free plan to automatically enable for the customer upon creation.
Whether to send email receipts to this customer. Defaults to
false.Array of fields to expand in the response. Available options:
invoices- Include customer invoicestrials_used- Include trial usage informationrewards- Include rewards informationentities- Include entity informationreferrals- Include referral informationpayment_method- Include payment method detailssubscriptions.plan- Expand full plan objects in subscriptionspurchases.plan- Expand full plan objects in purchasesbalances.feature- Expand full feature objects in balances
Response
Returns a Customer object with the following fields:Your unique identifier for the customer.
The name of the customer.
The email address of the customer.
Timestamp of customer creation in milliseconds since epoch.
The fingerprint identifier for the customer.
Stripe customer ID.
The environment this customer was created in (
sandbox or live).The metadata for the customer.
Whether email receipts are enabled for this customer.
Active and scheduled recurring plans that this customer has attached. Each subscription includes:
plan_id- The unique identifier of the subscribed planstatus- Current status (activeorscheduled)auto_enable- Whether the plan was automatically enabledadd_on- Whether this is an add-on planpast_due- Whether the subscription has overdue paymentsstarted_at- Timestamp when subscription startedcurrent_period_start- Start of current billing periodcurrent_period_end- End of current billing periodquantity- Quantity of the subscriptioncanceled_at- Timestamp when canceled (if applicable)expires_at- Timestamp when it expires (if applicable)trial_ends_at- Timestamp when trial ends (if applicable)
One-time purchases made by the customer.
Feature balances keyed by feature ID, showing usage limits and remaining amounts. Each balance includes:
feature_id- The feature identifiergranted- Total amount grantedremaining- Amount remainingusage- Total usageunlimited- Whether the feature is unlimitedoverage_allowed- Whether overage is allowedmax_purchase- Maximum purchasable amountnext_reset_at- Timestamp of next resetbreakdown- Detailed breakdown by entitlement