| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Get Account Connectivity Status
Returns the current Finicity connectivity status for a specified merchant, including whether the financial account link is active and the details of any connected bank accounts. This endpoint is used to verify that a merchant has successfully completed the bank account connection flow before proceeding with banking-dependent boarding steps.
Endpoint
GET /api/v1/getAccountConnectivityStatus
Authentication
Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:
Authorization: Basic {base64(username:password)}
When to use
Call this endpoint after initiating the Finicity account connection flow (GET /api/v1/connectFinancialAccount) and receiving the callback. It confirms that the merchant's bank account was linked successfully and provides the routing and account number details captured during the connection. This check is typically performed as part of the banking verification step in the underwriting or banking submission workflow.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | integer (int32) | Yes | The merchant profile ID to check for Finicity connectivity |
Response
200 OK
| Field | Type | Description |
|---|---|---|
| data.status | string | Human-readable connectivity status description |
| data.connected | boolean | true if the merchant's bank account is actively connected via Finicity |
| data.accounts | array | List of connected bank accounts |
| data.accounts[].bankName | string | Name of the connected bank institution |
| data.accounts[].routing | string | Bank routing number for the connected account |
| data.accounts[].account | string | Bank account number for the connected account |
| status | string | HTTP status label (e.g., OK) |
| error | string | Error message if the lookup failed |
| warning | string | Non-fatal warning message, if any |
| validationResults | array | List of field-level validation errors |
| requestId | integer | Unique identifier for this API request |
{
"data": {
"status": "connected",
"connected": true,
"accounts": [
{
"bankName": "First National Bank",
"routing": "021000021",
"account": "4072819305"
}
]
},
"status": "OK",
"error": null,
"warning": null,
"validationResults": [],
"requestId": 91384
}Error Codes
| Code | When it happens |
|---|---|
| 400 | id parameter is missing or not a valid integer |
| 401 | Invalid or missing Basic Auth credentials |
| 403 | User does not have permission for this operation |
| 404 | No connectivity data found for the given merchant id |
| 500 | Internal server error |
Common Mistakes
- Calling this endpoint before the merchant has completed the Finicity connection flow —
connectedwill befalseandaccountswill be empty until the merchant finishes linking their bank. - Treating an empty
accountsarray as an error — it is a normal response when the merchant has not yet connected an account. - Not polling this endpoint after sending the merchant through the connection flow — the callback updates the record, but you should verify the status before proceeding with banking submission.
- Confusing
data.status(a string description) withconnected(the authoritative boolean) — always checkconnectedto determine whether an account is linked.
Related Endpoints
GET /api/v1/connectFinancialAccount— generate the Finicity link to send to the merchant for account connectionPOST /api/v1/banking/submitBanking— submit banking information after connectivity is confirmedGET /api/v1/merchant/status— check the overall boarding status of the merchant
Example
curl -X GET "https://hq.staging.netevia.dev/api/v1/getAccountConnectivityStatus?id=48291" \
-H "Authorization: Basic $(echo -n 'username:password' | base64)"