UDA endpoints — statements
How to call the statement routes. The formal schema is the OpenAPI specification
(openapi/source/connector/parties/); this page is the call contract. Internal processing is in
the architecture reference; caveats in the implementation notes.
Both routes require a bearer token and party context (partyId).
statementId in the path is the Ark statement id.
| Method | Path | Code | Purpose |
|---|---|---|---|
GET | /v1/parties/statements | 200 | List the party's statements (paged) |
GET | /v1/parties/statements/{statementId} | 200 | Download a statement PDF |
Notes for callers
- List takes a
pagequery parameter (defaults to page 1) and returns statement metadata (statementId,vendorId,description,issuedAt,statementType). Only monthly statements are returned, and the response carries noaccountId(see the implementation notes). - Download streams the statement as a PDF (
application/pdf,Content-Disposition: attachment). Pass the ArkstatementIdfrom the list response. - If the core system cannot produce the file, the download fails with
500— see the implementation notes.
Errors
| HTTP | Code | When |
|---|---|---|
404 | PAR004001 | no party mapping for the caller (ClientAuthManager.getClientKey → PARTY_NOT_FOUND) |
404 | ACC004002 | no statement mapping for statementId |
500 | ACC100003 | download: the core system failed to return the file (CORE_BANKING_UNAVAILABLE; thrown via internalServerErrorException) |
404 | ACC004005 | list: no "Monthly Statements" statement type configured in the core system |
500 | ACC022001 | list: a returned statement has no id |