Returns data about whether Finicity is connected or not

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

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

ParameterTypeRequiredDescription
idinteger (int32)YesThe merchant profile ID to check for Finicity connectivity

Response

200 OK

FieldTypeDescription
data.statusstringHuman-readable connectivity status description
data.connectedbooleantrue if the merchant's bank account is actively connected via Finicity
data.accountsarrayList of connected bank accounts
data.accounts[].bankNamestringName of the connected bank institution
data.accounts[].routingstringBank routing number for the connected account
data.accounts[].accountstringBank account number for the connected account
statusstringHTTP status label (e.g., OK)
errorstringError message if the lookup failed
warningstringNon-fatal warning message, if any
validationResultsarrayList of field-level validation errors
requestIdintegerUnique 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

CodeWhen it happens
400id parameter is missing or not a valid integer
401Invalid or missing Basic Auth credentials
403User does not have permission for this operation
404No connectivity data found for the given merchant id
500Internal server error

Common Mistakes

  • Calling this endpoint before the merchant has completed the Finicity connection flow — connected will be false and accounts will be empty until the merchant finishes linking their bank.
  • Treating an empty accounts array 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) with connected (the authoritative boolean) — always check connected to determine whether an account is linked.

Related Endpoints

  • GET /api/v1/connectFinancialAccount — generate the Finicity link to send to the merchant for account connection
  • POST /api/v1/banking/submitBanking — submit banking information after connectivity is confirmed
  • GET /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)"
Query Params
int32
required
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/json
data
status
requestId