Explore Finch developers’ most frequently asked questions (FAQ) and answers. Topics include Products & Integrations, API & Data Model, Security, and more.
/individual
, /employment
, and /pay-statement
endpoints are special because they are “batch” endpoints, meaning you can send as many ids as you want in the body, and get a single response back containing the information for as many individuals/pay-statements as you sent. Query parameters can’t handle 1000 ids in the URL, hence the need for POSTs using request bodies.
end_date
and debit_date
.
NULL
fields when values exist in the system andNULL
can be potentially indicative of 4 things:NULL
over time; if the data is available in the provider’s system, Finch should be returning that data. Keep in mind that the status of an employee (full-time vs contractor) can also affect which fields return NULL.
Finch defines the “rate of incorrect data” as data that does not match what is reported in the provider’s system. This could either mean the field returns blank indicating a potential bug in our code (e.g.: a pay statement array returns empty), or the field returns a value that does not reflect what is reported in the system. We have an internal dashboard where we track data field coverage and correctness in real-time. We have alerts defined to notify us of any anomalies detected which we proactively investigate and fix.
There are several ways developers can validate data coming from Finch:
payroll_provider=<your_provider_name>
into the /authorize
url when opening Finch Connect.
access_token
lifetime is infinite; it does not expire, unless you disconnect it. If a 401 Re-authentication
error is received (either by a user changing their security setting or an employment system makes an infrastructure change), Finch’s connection can get disconnected, which requires a user to reauthenticate and a new Finch access_token will be created and sent back to your app.