Get Financial Account Number

This endpoint retrieves the financial account number and routing number for one or more financial accounts linked to a specified customer profile. It provides secure, authenticated access to sensitive account identifiers required for transactions and account management operations. Only authorized users with a valid Bearer token may access this information.

Endpoint

GET /netevia/financialAccount/number

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 you need to retrieve the full account number and routing number for a customer's financial account — for example, to prefill wire transfer details, set up ACH payments, or display account information within a partner application. This is typically called after a financial account has been created and verified. Because account numbers are sensitive, always ensure the requesting user is properly authenticated and authorized before surfacing the returned values in any UI.

Query Parameters

Response

200 OK

Returns an array of financial account objects, each containing restricted account details.

Top-level array item (bank.client.financialaccount.restricteddetails):

node object (bank.client.financialaccount.noderestricteddetails):

node.restrictedDetails object (bank.client.financialaccount.restricteddetailsdata):

[
  {
    "id": "fa_0987654321",
    "name": "Business Checking",
    "created": "2024-03-15T10:22:00Z",
    "accountStatus": "ACTIVE",
    "node": {
      "id": "node_1122334455",
      "restrictedDetails": {
        "typename": "CHECKING",
        "number": "XXXXXXXXXX",
        "routingNumber": "021000021"
      }
    }
  }
]

Error Codes

Common Mistakes

• Passing a profileId that belongs to a different partner or an unauthorized customer will result in a 403 or empty response — always verify the profile belongs to the authenticated session's partner context.
• Caching the returned account number or routing number in plaintext storage is a security risk; treat these values as sensitive credentials and store them encrypted.
• Forgetting to refresh the Bearer token before it expires (10-minute lifetime) will result in a 401 error mid-flow when retrieving account details.

Related Endpoints

• POST /api/auth/v2 — Obtain a Bearer token for authentication
• POST /api/auth/refresh — Refresh an expiring Bearer token
• GET /netevia/financialAccount — List financial accounts for a customer profile
• POST /netevia/financialAccount — Create a new financial account for a customer

Example

curl -X GET "https://api.banking.netevia.dev/netevia/financialAccount/number?profileId=10045" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"