Search for Business Account Holders
The Search for Business Account Holders endpoint allows partners and administrators to query the Netevia banking system for business account holders using a variety of search parameters. It returns a list of matching business accounts with their identifiers and doing-business-as (DBA) names. This endpoint is essential for customer support workflows, account administration, and partner-level account management operations.
Endpoint
POST /api/AccountsSearch/BusinesAccountHolder
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 locate one or more business account holders by name (DBA), ISO relationship, or a set of agent IDs. It is suited for customer service lookups, administrative dashboards, and partner reporting tools that need to surface business account records quickly without knowing the exact account ID. The count parameter allows callers to limit result set size for performance-sensitive queries.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| agentIds | array of integer (int32) | No | List of agent IDs to filter results to accounts associated with specific agents. |
| isoId | integer (int32) | No | ISO (Independent Sales Organization) ID to scope the search to accounts under a particular ISO. |
| dba | string | No | Doing-business-as name (full or partial) to search for matching business account holders. |
| count | integer (int32) | No | Maximum number of results to return. |
{
"agentIds": [101, 102],
"isoId": 55,
"dba": "Acme Supplies",
"count": 25
}Response
200 OK
Returns an array of business account holder search results matching the provided criteria.
| Field | Type | Description |
|---|---|---|
| id | integer (int32) | Unique identifier of the business account holder. |
| dba | string | Doing-business-as name of the business account holder. |
[
{
"id": 1042,
"dba": "Acme Supplies LLC"
},
{
"id": 1078,
"dba": "Acme Supplies East"
}
]Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields or validation error |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions |
| 404 | Resource not found |
| 500 | Internal server error |
Common Mistakes
- Sending an empty request body without any filter fields — at least one search parameter (
agentIds,isoId, ordba) should be provided to produce meaningful results rather than returning all accounts or an empty set. - Omitting the
countfield on large data sets — without a limit, the response may return a very large number of records, impacting performance; always specify a reasonablecountvalue. - Using an expired Bearer token — tokens are valid for only 10 minutes; refresh via
POST /api/auth/refreshbefore making calls if the token may have expired. - Providing an exact full legal name when the field represents the DBA (doing-business-as) name — ensure search strings match the DBA name, not the registered legal entity name.
Related Endpoints
POST /api/AccountsSearch/PersonalAccountHolder— Search for personal (consumer) account holders using similar criteria.POST /api/auth/v2— Obtain a Bearer token required for authentication.POST /api/auth/refresh— Refresh an existing Bearer token before it expires.
Example
curl -X POST https://api.banking.netevia.dev/api/AccountsSearch/BusinesAccountHolder \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"agentIds": [101, 102],
"isoId": 55,
"dba": "Acme Supplies",
"count": 25
}'