1. Docs
  2. API Reference
  3. Summarize the Account's invoices

Summarize the Account's invoices

GET/api/v1/billing/invoices/summary

Returns { data } with totals across every invoice of the Account, for the Billing summary and the payment banner: billed_this_year, due and paid (amount in the currency's minor unit, and count), latest_charged_amount, and payable_invoice, the oldest open or uncollectible invoice. Free Accounts with no Stripe customer get zeros and nulls.

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

  • dataInvoicesSummaryResponseDto*

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

Request
curl -X GET "https://auth.canopy-io.com/api/v1/billing/invoices/summary" \
  -H "X-API-Key: $CANOPY_API_KEY"
Response
{
  "data": {
    "currency": "string",
    "year": 0,
    "billed_this_year": {
      "amount": 0,
      "count": 0
    },
    "due": {
      "amount": 0,
      "count": 0
    },
    "paid": {
      "amount": 0,
      "count": 0
    },
    "latest_charged_amount": 0,
    "payable_invoice": {
      "id": "string",
      "number": "string",
      "status": "draft",
      "amount": 0,
      "amount_due": 0,
      "currency": "string",
      "description": "string",
      "period_start": "2026-04-20T12:00:00.000Z",
      "period_end": "2026-04-20T12:00:00.000Z",
      "due_date": "2026-04-20T12:00:00.000Z",
      "collection_method": "charge_automatically",
      "created": "2026-04-20T12:00:00.000Z",
      "hosted_invoice_url": "string",
      "invoice_pdf": "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
GETPreview the Account's next invoice
Was this page helpful?

Tell us how we can improve this guide.