Opens a new financial account for a customer within the Netevia Banking platform.
Open Financial Account
The Open Financial Account endpoint allows partners to create a new financial account for a customer within the Netevia Banking platform. By supplying the required account name and an optional application identifier, the API provisions the account and returns a confirmation string. Both personal and business customers may open accounts, subject to the platform limit of up to 5 financial accounts per customer.
Endpoint
POST /api/financialAccounts/open
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 onboarding a new customer and a financial account needs to be created for them, or when an existing customer requests an additional account (checking, savings, or other supported account types). It is also used during programmatic account setup flows where an external application ID must be linked to the new account for downstream reconciliation.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| Name | string | Yes | The display name for the new financial account (e.g., "Business Checking", "Personal Savings"). |
| OpenApplicationId | string | No | An external application or workflow identifier to associate with the account opening request, used for tracking and reconciliation. |
Response
200 OK
The response is a plain string confirming the result of the account creation request (e.g., the new account identifier or a status message).
| Field | Type | Description |
|---|---|---|
| (body) | string | Confirmation value returned upon successful account creation, typically the new account ID or a status indicator. |
"acc_9f3a2d1e7c4b"Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields or validation error (e.g., Name query parameter not provided) |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions or customer has reached the maximum number of allowed financial accounts |
| 404 | Resource not found (e.g., referenced customer or application ID does not exist) |
| 500 | Internal server error |
Common Mistakes
- Omitting the required
Namequery parameter, which causes a 400 validation error. - Attempting to open more than 5 financial accounts for a single customer without requesting a limit increase.
- Passing an expired Bearer token; tokens expire after 10 minutes and must be refreshed before making account creation calls.
- Sending account details in a JSON request body instead of as query parameters — this endpoint uses query parameters exclusively.
Related Endpoints
GET /api/financialAccounts— Retrieve a list of financial accounts for the authenticated customerGET /api/financialAccounts/{id}— Retrieve details for a specific financial accountPOST /api/auth/v2— Obtain a Bearer token for authenticationPOST /api/auth/refresh— Refresh an existing Bearer token
Example
curl -X POST "https://api.banking.netevia.dev/api/financialAccounts/open?Name=Business%20Checking&OpenApplicationId=app-20240601-001" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"