Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: OAuth 2.0 (client credentials).
  • Connection: Veryfront obtains machine-to-machine tokens from the client ID and secret in the project’s environment variables.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. Get client credentials: Request finAPI Access credentials (client_id and client_secret) from finAPI at https://www.finapi.io/en/contact-us/. New customers start with a free sandbox client; the Live environment requires a license agreement.
  2. Set environment variables: Add FINAPI_CLIENT_ID and FINAPI_CLIENT_SECRET to your .env.
  3. Verify access: Run Get Client Configuration. Access tokens are minted automatically via the OAuth2 client_credentials grant against https://live.finapi.io/api/v2/oauth/token - no user login is involved.

​
Provider notes

  • This connector pins the Live environment (live.finapi.io). For sandbox testing, point a copy of the connector at sandbox.finapi.io - the token and API paths are identical. Live access may additionally be IP-restricted.
  • Most finAPI data endpoints (bank connections, accounts, transactions, securities) require a USER access token obtained per end user via the password grant. The client_credentials token used here only covers client-level endpoints: bank catalog search, client configuration, and user provisioning.
  • Users created on the Live instance count towards your finAPI license agreement.
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as finapi__search_banks with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.