Checks & Pending Results

How API calls are counted, and what to do when a result comes back before its source has answered.

How Checks Are Counted

  • Each call to a per-service endpoint, such as validate/irs-tin-name-matching, uses one check.
  • A call to validate also uses one check, whether it runs one service or several.
  • An EIN lookup by name includes one reveal-ein call for the candidate you choose, at no extra check.
  • request-details and history return results you already have and do not run anything again.

When a Result Is Not Ready

Almost every result comes back in the same response. When an upstream source, such as the IRS, is unavailable, that service's result has completed: false and TIN Comply retries it automatically. Keep the id from the response and call request-details with it later. Once the result shows completed: true, it is final.

The cURL and Java tabs show the request-details call on its own; the others show the whole flow. request-details needs a key with the History permission.

curl -X POST https://www.tincomply.com/api/v1/request-details \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "id": "BG5CF5Z2q0SwIBmhZylJggxp" }'