In a full implementation, Finch requires both a frontend and a backend application to exist. The frontend application coordinates connecting the employer’s system, and the backend server securely manages the requests and responses to and from Finch APIs.
Use this Implementation Guide and Go Live Checklist to set up your frontend and backend applications. You will sign up for a Finch Account, set up Finch Connect, integrate the Finch API, and go into production.
client_secret
in a backend data store. It should never be exposed client-side. It is recommended to store it encrypted.client_secret
should remain on the backend, you should always perform an authorization code
for an access_token
exchange only on your back-end server and never on the client-side./disconnect
endpoint to disconnect a user’s employment system from your application. Ensure that all teams that will be managing the Finch integration can easily disconnect tokens or know the process to request a disconnect.connection_id
alongside the access token and use it when contacting Finch Support about an issue.finch-request-id
for every response, whether successful or unsuccessful./individual
, /employment
, /pay-statement
), send multiple ids in a single request to the Finch API to reduce the number of requests your application makes.Once you have tested your Finch integration with test accounts, you can go live.
In a full implementation, Finch requires both a frontend and a backend application to exist. The frontend application coordinates connecting the employer’s system, and the backend server securely manages the requests and responses to and from Finch APIs.
Use this Implementation Guide and Go Live Checklist to set up your frontend and backend applications. You will sign up for a Finch Account, set up Finch Connect, integrate the Finch API, and go into production.
client_secret
in a backend data store. It should never be exposed client-side. It is recommended to store it encrypted.client_secret
should remain on the backend, you should always perform an authorization code
for an access_token
exchange only on your back-end server and never on the client-side./disconnect
endpoint to disconnect a user’s employment system from your application. Ensure that all teams that will be managing the Finch integration can easily disconnect tokens or know the process to request a disconnect.connection_id
alongside the access token and use it when contacting Finch Support about an issue.finch-request-id
for every response, whether successful or unsuccessful./individual
, /employment
, /pay-statement
), send multiple ids in a single request to the Finch API to reduce the number of requests your application makes.Once you have tested your Finch integration with test accounts, you can go live.