Skip to main content

Platform — statements endpoints

How to call the platform statement routes. The formal schema is the OpenAPI specification (openapi/source/platform/parties/parties.yml); this page is the call contract.

Statements are read-only — there is no lifecycle file. All routes require a bearer token (B2B JWT) with the CLIENT role and an ACTIVE party context. The global /v1 prefix applies.

Route summary

MethodPathCodePurpose
GET/v1/parties/statements200List party statements
GET/v1/parties/statements/{statementId}200Download a statement file

GET /v1/parties/statements — list statements

Query parameters:

NameTypeRequiredDefaultDescription
pageintegerno1Page of results (standard pagination)

Response: { statements: Statement[] }. Each item includes statementId, vendorId, statementType (MONTHLY), issuedAt, and a description.

Returns 500 ACC004005 if the statement type cannot be found.

GET /v1/parties/statements/{statementId} — download a statement

Returns a file stream. The response Content-Type and Content-Disposition headers are forwarded from the provider's response. The OAS declares application/pdf as the media type but the actual content type is determined by the provider at runtime and may differ.

statementId must have been obtained from a prior list call.

Errors

HTTPCodeWhen
401GEN001002/4/5/6Invalid or missing token
403GEN003005/6Client or party inactive
404ACC004002Statement not found at the provider
500ACC004005Statement type (MONTHLY) not found at the provider
500ACC022001The provider cannot resolve the statement id
500GEN100001Downstream communication failure with the provider