Skip to content
/
Download a managed card s...

Download a managed card statement as a PDF

Request

Returns the statement for the managed card identified by the id path parameter as a PDF document, suitable for delivery to the end customer.

Every date and time on the document is rendered in timezone, and startPeriod and endPeriod are resolved to local midnight in that timezone. The PDF carries a label stating which timezone it was rendered in. When timezone is omitted the document renders in UTC.

Unlike the JSON statement endpoint, this returns every entry in the period rather than a single page. A period longer than 12 months, or one containing more than 5,000 entries, is rejected with a 400 rather than silently truncated — narrow the period and request again.

Pre-paid mode cards hold their own balance, so the opening and closing balances refer only to the requested card. Debit-mode cards do not hold a balance — their activity posts to the parent Managed Account — so their document omits the balance column.

A period containing no entries produces a valid PDF with no entry rows.

Security
auth_token and api-key
Path
idstring^[0-9]+$required

The unique identifier of the managed card.

Query
startPeriodstring, (date)

First day of the statement period, inclusive, as a date in the format yyyy-MM-dd.

Interpreted as local midnight in timezone. Defaults to one month before endPeriod.

Example:startPeriod=2026-08-01
endPeriodstring, (date)

Last day of the statement period, inclusive, as a date in the format yyyy-MM-dd.

Interpreted as local midnight in timezone, so the period ends at the final moment of this day in that timezone. Defaults to today in timezone. The period must not exceed 12 months.

Example:endPeriod=2026-08-31
timezonestring

IANA timezone used to render every date and time on the PDF, and to resolve startPeriod and endPeriod to local midnight. Defaults to UTC.

Only IANA timezone names are accepted, for example Europe/Rome or America/New_York. Fixed offsets such as +02:00 or GMT+2 are rejected, because they carry no daylight-saving rules and would render incorrect times across a transition.

Example:timezone=Europe/Rome
curl -i -X GET \
  'https://sandbox.weavr.io/multi/managed_cards/{id}/statement/pdf?startPeriod=2026-08-01&endPeriod=2026-08-31&timezone=Europe%2FRome' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'api-key: YOUR_API_KEY_HERE'

Responses

The generated PDF statement

Bodyapplication/pdf
string, (binary)
Response
string