1. Docs
  2. API Reference
  3. Preview the Account's next invoice

Preview the Account's next invoice

GET/api/v1/billing/invoices/upcoming

Returns the next invoice Stripe would issue for the Account's subscription — line items (each flagged when it is a proration), subtotal, tax, total, currency and the expected issue date. Every figure comes from Stripe's own invoice preview, so the dashboard renders what the customer will actually be charged rather than a locally-computed estimate. Free Accounts with no Stripe subscription receive null.

Authentication

Bearer TokenAuthorization Option A

JWT access token. Never send alongside X-API-Key: a request carrying both is refused.

API KeyX-API-Key Option B

API key for management-tier access. Never send alongside an Authorization header: a request carrying both is refused.

Requires permission billing.viewAccount

Read the subscription, the plan, usage and invoices. A scoped API key must hold it as a scope; a full-access key holds every scope within its Environment except the named-only and account scopes; a developer's token needs the Console capability that covers it. A credential without it is refused with 403.

Responses

application/json

  • dataUpcomingInvoiceResponseDto*

application/json

  • errorApiErrorBodyDto*

application/json

  • errorApiErrorBodyDto*

application/json

  • errorApiErrorBodyDto*

Errors

When the request can't be completed, the response body includes a stable error code you can branch on, and a correlation_id (also sent as the X-Correlation-Id header). Quote the correlation id when you contact support: it identifies the exact request in Canopy's logs. A request refused by an authorization check answers 403 with the code authorization.denied, and its data names the denial_reason and the permission checked.

403authorization.deniedForbidden
When it happens

The credential does not hold the permission this operation checks: a scoped API key without the scope, a developer without the Console capability that covers it, or a permission granted somewhere other than the node the request targets. The error's data names the permission.

Remediation

Add the permission named in the Authentication section to the key's scopes, or ask an account administrator to grant the covering capability, then retry. For a node-scoped operation, make sure the grant reaches the node you are acting on.

Returned object

UpcomingInvoiceResponseDtoView all properties on this resource
Request
curl -X GET "https://auth.canopy-io.com/api/v1/billing/invoices/upcoming" \
  -H "X-API-Key: $CANOPY_API_KEY"
Response
{
  "data": {
    "lines": [
      {
        "description": "string",
        "amount": 0,
        "proration": false
      }
    ],
    "subtotal": 0,
    "tax": 0,
    "total": 0,
    "currency": "string",
    "next_payment_at": "string"
  }
}
 Related endpoints
GETGet the Account's current subscription
GETGet the Account's current plan usage
GETGet the Account's plan-feature entitlements
GETList the purchasable plan prices
GETList the Account's invoices
GETSummarize the Account's invoices
 Was this page helpful?

Tell us how we can improve this guide.

Canopy