Skip to main content

​
Null Values

Finch returns null for a field on a record when:
  1. the employment system doesn’t support the field,
  2. the employment system supports the field but the payroll administrator hasn’t filled in the data, or
  3. Finch can’t infer a reasonable value (for example, the categorization of a tax).
Null-ness is per record, not per field — one individual may have a value where another doesn’t. Check a field’s value for null before operating on it — for example, before calling a string method or accessing a nested property — rather than assuming every record has a value.
Check a field’s value for null before operating on it. Don’t assume every record has a value just because other records do.

​
202 Response Codes

Requests to the Finch API can return a 202 Accepted response. This means the connection exists but the data isn’t available yet — common for async operations. Once the data is available, Finch stops returning 202 for that request. Requests that can return a 202 response include: Handle a 202 response by:
  • Retrying the request after a delay. For assisted connections, the SLA for the first data sync is 14 days.
  • Backing off — increase the delay between retries if the response keeps returning 202.
  • Not processing the response body as data until you receive a successful response.
Examples of 202 Responses:
See Testing assisted integrations to simulate the pending state that produces a 202 response in the Finch Sandbox.