> ## Documentation Index
> Fetch the complete documentation index at: https://developer.tryfinch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Handling API Responses

> Handle null values and 202 responses from the Finch API — why each occurs and the retry, backoff, and null-check behavior your application should implement.

## 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>
  Check a field's value for `null` before operating on it. Don't assume every record has a value just because other records do.
</Check>

## 202 Response Codes

Requests to the Finch API can return a [`202 Accepted`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/202) 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:

* [Assisted Connect](/integrations/providers#integration-types), including [Assisted Deductions](/implementation-guide/API-Calls/Write-Data#assisted-deductions)
* [Pay statements](/developer-resources/Data-Syncs#pay-statements) that exist but haven't been fetched yet
* [Authentication fallback](/implementation-guide/Integration-Preparation/Configure-Auth-Methods#set-up-authentication-fallback)

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:

```json theme={null}
{
  "code": 202,
  "name": "accepted",
  "finch_code": "data_sync_in_progress",
  "message": "The pay statements for this payment are being fetched. Please check back later."
}

{
   "code": 202,
   "name": "authorization_pending",
   "finch_code": "pending",
   "message": "Authorization to this company's data is pending"
}
```

See [Testing assisted integrations](/implementation-guide/Test/Finch-Sandbox#testing-assisted-integrations) to simulate the pending state that produces a `202` response in the Finch Sandbox.