API references
Search documentation... ⌘K
API references
Merchant API

List statements

Returns a paginated list of statements for the authenticated merchant grouped by month.

The response includes month-based pagination where each page contains all statements for a specific month.

The response includes cursor-based pagination with previous and next cursors that can be used to navigate through months.

Endpoint signature
This endpoint requires an API key. Read our authentication guide for more information.
POST https://api.reservepay.com/merchants/list-statements HTTP/1.1
Content-Type: application/json
Accept: application/json
Authorization: Bearer <token>
{
month: string?,
}
Returns: object
New to Reservepay? Read our guide on how to call endpoints to get started. Note that this endpoint returns a paginated response, see the Pagination section of the same guide.
Request arguments
month string

Optional. Month to retrieve statements for in YYYY-MM format (default: current month)

Response attributes
Attribute Description
previous
object

Cursor for the previous month. Contains 'before' (YYYY-MM format) parameter. Use these values in the 'month' parameter of the next request to get the previous month.

page
array

The current month's statements, ordered by day (newest first).

next
object

Cursor for the next month. Contains 'after' (YYYY-MM format) parameter. Use these values in the 'month' parameter of the next request to get the next month.

Errors specific to this endpoint
invalid_month

Invalid month format. Expected YYYY-MM format (e.g., '2024-12')

Errors common to all endpoints
UNHANDLED_ERROR

This error occurs when the server encounters an unexpected internal error that it cannot handle gracefully. This typically happens due to bugs, infrastructure issues, or edge cases that weren't anticipated during development.

INVALID_ARGUMENTS

This error occurs when the request contains invalid or missing parameters. Common cases include missing required fields, or values that don't match the expected format or type.

BAD_VERSION

This error occurs when making requests to an API version that does not exist. This commonly happens when using an outdated SDK or when the API version specified in the request URL is incorrect.

CODE SAMPLES
curl
Learn how to run these code samples in your terminal by reading our guide.