/v1/account/billing-historyBilling history
billing:readThe account invoice history read live from Stripe (plan, amount, date, payment status, and receipt links), with cursor pagination. Empty for accounts with no Stripe customer.
Query parameters
limitinteger default: 20min 1, max 50startingAfterstringmax 256 chars
Responses
200A page of invoicesinvoicesarray of InvoiceView requiredInvoices for this account, newest first.
idstring requiredThe Stripe invoice id.
createdstring requiredWhen the invoice was issued, as an ISO 8601 instant.
amountnumber requiredInvoice total in the currency’s SMALLEST unit, as Stripe reports it: 4900 means $49.00, not $4,900.
currencystring requiredISO 4217 currency code, lower-case, as Stripe reports it.
statusstring requiredThe Stripe invoice status (`paid`, `open`, and so on).
planNamestring requiredThe plan this invoice was for.
hostedInvoiceUrlstring | null requiredStripe-hosted page for viewing and paying the invoice. Null when Stripe provides none.
invoicePdfUrlstring | null requiredThe invoice PDF. A different document from `receiptUrl`: this is what was billed.
receiptUrlstring | null requiredThe payment receipt. A different document from `invoicePdfUrl`: this is proof of payment. Null until paid.
hasMoreboolean requiredTrue when more invoices exist beyond this page.
401No or invalid credentialcodestring requiredStable machine-readable error code. Branch on this, never on the numeric status.
bad_requestunauthorizedsignature_requiredpayment_requiredforbiddennot_foundconflictgonepayload_too_largeunprocessable_entitytoo_many_requestsinternal_errornot_implementedbilling_unavailablenot_contactablemailbox_link_unavailablemailbox_requiredmail_engine_unavailablewebhook_publisher_unavailabledatabase_unavailableclient_errormessagestring requiredHuman-readable explanation of the refusal.
statusinteger requiredThe HTTP status code, repeated in the body.
remedyobjectA self-serve path forward, when one exists (a 402 points at the credit top-up).
kindstring requiredWhat kind of remedy this is, so a client can route it: whether the caller can clear the condition through the API, or a person must act in the web app.
topupconnect_mailboxurlstring requiredWhere to go to clear the condition: an API path, or a web app page when only a person can.
403Missing billing:readcodestring requiredStable machine-readable error code. Branch on this, never on the numeric status.
bad_requestunauthorizedsignature_requiredpayment_requiredforbiddennot_foundconflictgonepayload_too_largeunprocessable_entitytoo_many_requestsinternal_errornot_implementedbilling_unavailablenot_contactablemailbox_link_unavailablemailbox_requiredmail_engine_unavailablewebhook_publisher_unavailabledatabase_unavailableclient_errormessagestring requiredHuman-readable explanation of the refusal.
statusinteger requiredThe HTTP status code, repeated in the body.
remedyobjectA self-serve path forward, when one exists (a 402 points at the credit top-up).
kindstring requiredWhat kind of remedy this is, so a client can route it: whether the caller can clear the condition through the API, or a person must act in the web app.
topupconnect_mailboxurlstring requiredWhere to go to clear the condition: an API path, or a web app page when only a person can.