Get Customer
Fetches a customer by ID, optionally expanding related data such as invoices or entities.
Use this when you know the customer exists or assert they exist without creating them.
Body Parameters
Response
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Body
ID of the customer to fetch
Expand related customer data like invoices or entities, or expand nested objects like balances.feature, flags.feature, subscriptions.plan, and purchases.plan.
invoices, trials_used, rewards, entities, referrals, payment_method, subscriptions.plan, purchases.plan, balances.feature, flags.feature, billing_controls.auto_topups.purchase_limit Response
OK
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.
A unique identifier (eg. serial number) to de-duplicate customers across devices or browsers. For example: apple device ID.
Stripe customer ID.
The environment this customer was created in.
sandbox, live The metadata for the customer.
Whether to send email receipts to the customer.
Billing controls for the customer (auto top-ups, etc.)
Active and scheduled recurring plans that this customer has attached.
One-time purchases made by the customer.
License seat pools granted by the customer's plans, with seat counts.
Feature balances keyed by feature ID, showing usage limits and remaining amounts.
Boolean feature flags keyed by feature ID, showing enabled access for on/off features.
Configuration for the customer.
Payment processors this customer is connected to (Stripe, Vercel, RevenueCat). Omitted entirely when the customer has not been created in any processor.
Invoices for this customer.
Entities associated with this customer.
Trial usage history for this customer.
Rewards earned or applied for this customer.
Referral records for this customer.
The customer's default payment method.