Download Bank Details by Financial Account
The GET /BankingRequisites endpoint retrieves detailed banking information associated with a specific financial account. It returns essential data such as account number, routing number, branch name, SWIFT code, and IBAN, packaged as a downloadable file. Only authenticated users can access this sensitive information, ensuring security and privacy throughout the process.
Endpoint
GET /BankingRequisites
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2
Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint when a partner application or end user needs to retrieve the full banking details for a financial account — for example, to display account and routing numbers for ACH setup, share account information for wire transfers, or download a bank confirmation document. This endpoint is commonly called during account onboarding flows, transaction setup, or whenever a user needs to share their banking details with a third party.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| financialAccountId | string | Yes | The unique identifier of the financial account whose banking requisites are to be retrieved. |
Response
200 OK
| Field | Type | Description |
|---|---|---|
| name | string (nullable) | The filename of the returned bank details document (e.g., a PDF or text file name). |
| content | string (nullable) | The base64-encoded or raw content of the bank details file. |
| contentType | string (nullable) | The MIME type of the returned content (e.g., application/pdf, text/plain). |
{
"name": "bank_details_XXXXXXXXXX.pdf",
"content": "JVBERi0xLjQKJeLjz9MKNiAwIG9iago...",
"contentType": "application/pdf"
}Error Codes
| Code | When it happens |
|---|---|
| 400 | The financialAccountId is missing, malformed, or does not correspond to a valid account. |
| 401 | Token missing, expired, or invalid. |
| 403 | Insufficient permissions — the authenticated user does not have access to the specified financial account. |
| 404 | No financial account found for the provided financialAccountId. |
| 500 | Internal server error. |
Common Mistakes
- Omitting the
financialAccountIdquery parameter — the endpoint requires it to identify which account's banking details to return. - Passing a
financialAccountIdthat belongs to a different customer or partner — the API will return a 403 or 404 rather than cross-account data. - Not decoding the
contentfield before rendering — if the responsecontentTypeisapplication/pdf, thecontentvalue is base64-encoded and must be decoded before saving or displaying. - Using an expired Bearer token — tokens are valid for 10 minutes; refresh via
POST /api/auth/refreshbefore calling this endpoint.
Related Endpoints
GET /FinancialAccounts— list all financial accounts for a customerGET /FinancialAccount/{financialAccountId}— retrieve details of a specific financial accountPOST /api/auth/v2— obtain a Bearer tokenPOST /api/auth/refresh— refresh an existing Bearer token
Example
curl -X GET "https://api.banking.netevia.dev/BankingRequisites?financialAccountId=YOUR_FINANCIAL_ACCOUNT_ID" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"