Download Bank Letter as PDF
The Download Bank Letter endpoint retrieves an official bank letter in PDF format containing a customer's essential banking details, including account numbers and bank name. This document is suitable for sharing banking details with third parties, satisfying KYC or compliance requirements, or maintaining personal records. Proper authentication is required to ensure secure access to sensitive account information.
Endpoint
GET /netevia/bankingrequisites
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint when a customer needs an official bank letter document — for example, to provide proof of banking details to a payroll provider, a landlord, or another financial institution. It is also useful for generating on-demand documentation within a partner application whenever a customer needs to download or share their banking requisites.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| profileId | integer (int32) | No | The numeric identifier of the customer profile whose bank letter is to be retrieved. |
| financialAccountId | string | No | The identifier of the specific financial account for which the bank letter should be generated. |
Response
200 OK
| Field | Type | Description |
|---|---|---|
| name | string (nullable) | The filename of the returned document (e.g., "bank_letter.pdf"). |
| content | string (nullable) | The Base64-encoded content of the PDF file. |
| contentType | string (nullable) | The MIME type of the returned file (e.g., "application/pdf"). |
{
"name": "bank_letter.pdf",
"content": "JVBERi0xLjQKJeLjz9MKMSAwIG9iago8PC9UeXBlL0NhdGFsb2cvUGFnZXMgMiAwIFI+PgplbmRvYmoK...",
"contentType": "application/pdf"
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing or invalid profileId or financialAccountId parameter format |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to access the specified profile or financial account |
| 404 | Profile or financial account not found |
| 500 | Internal server error |
Common Mistakes
- The
contentfield in the response is Base64-encoded. You must decode it before writing it to a file or displaying it as a PDF. - Omitting both
profileIdandfinancialAccountIdmay result in an ambiguous request; always supply at least theprofileIdto identify the correct customer. - Ensure the Bearer token is still valid (tokens expire after 10 minutes) before making this request — an expired token will return a 401 error.
Related Endpoints
GET /netevia/statement— Download a financial account statement as a PDFGET /netevia/profile/{profileId}— Retrieve customer profile detailsGET /netevia/financialaccounts— List all financial accounts for a customer
Example
curl -X GET "https://api.banking.netevia.dev/netevia/bankingrequisites?profileId=12345&financialAccountId=XXXXXXXXXX" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Accept: application/json"