Download bank details by financial account

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

ParameterTypeRequiredDescription
financialAccountIdstringYesThe unique identifier of the financial account whose banking requisites are to be retrieved.

Response

200 OK

FieldTypeDescription
namestring (nullable)The filename of the returned bank details document (e.g., a PDF or text file name).
contentstring (nullable)The base64-encoded or raw content of the bank details file.
contentTypestring (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

CodeWhen it happens
400The financialAccountId is missing, malformed, or does not correspond to a valid account.
401Token missing, expired, or invalid.
403Insufficient permissions — the authenticated user does not have access to the specified financial account.
404No financial account found for the provided financialAccountId.
500Internal server error.

Common Mistakes

  • Omitting the financialAccountId query parameter — the endpoint requires it to identify which account's banking details to return.
  • Passing a financialAccountId that belongs to a different customer or partner — the API will return a 403 or 404 rather than cross-account data.
  • Not decoding the content field before rendering — if the response contentType is application/pdf, the content value 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/refresh before calling this endpoint.

Related Endpoints

  • GET /FinancialAccounts — list all financial accounts for a customer
  • GET /FinancialAccount/{financialAccountId} — retrieve details of a specific financial account
  • POST /api/auth/v2 — obtain a Bearer token
  • POST /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"
Query Params
string
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
text/plain
application/json
text/json