API Endpoint: Request Details

This endpoint retrieves the details of a specific validation request, returning the original request and its results.

POST /api/v1/request-details

https://www.tincomply.com/api/v1/request-details

Returns the complete stored result of one earlier validation request: the original request and every result object, in the same shape as the validate response. GET with ?id= also works.

Request body

FieldTypeDescription
idrequired string The request id returned by a validate call.

Returns 400 when the id is malformed and 404 when no request with that id belongs to your account, both in the url-and-errors format shown on the overview. Requires an API key with the History permission.

What to do with this result

When you seeDo this
A result still has completed falseThat source has not answered yet. Call request-details again later.
404The id is not on your account. Check that you are using a key for the account that made the request.

Sample request

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":"BZ5CF5Z2q0SwIBmhZylJggxp"}'

Sample response

{
  "id": "BZ5CF5Z2q0SwIBmhZylJggxp",
  "requestedBy": "ERP integration",
  "request": {
    "tin": "XXXXX1234",
    "name": "JOHN SMITH",
    "requestDate": "2026-10-01T20:23:41Z",
    "requestedServices": "irs-tin-name-matching"
  },
  "irsTinNameMatchingResult": {
    "message": "TIN and Name combination does not match IRS records",
    "result": 3,
    "completed": true
  }
}

POST /api/v1/history

https://www.tincomply.com/api/v1/history

Lists your previous validation requests, newest first, with a summary result for each service.

Request body

FieldTypeDescription
page int Page number, starting at 1.
count int Page size.
search string Optional free-text filter, such as a name or TIN fragment.
includeApi bool Include requests made with API keys, not only portal requests.

Values for the *ResultType fields

ValueMeaning
0Unrequested
1Unprocessed
2Bad
3Good
4Pending
5Indifferent
6Information

Each item includes a ResultType field only for the services that ran on that request. requestState: 0 unprocessed, 1 in process, 2 processed, 3 retry, 4 failure.

What to do with this result

When you seeDo this
requestState is 0, 1 or 3Still working. Call request-details with the item's id later for the full result.
A ResultType is 2 (Bad)Call request-details with the item's id to see exactly what failed.

Sample request

curl -X POST https://www.tincomply.com/api/v1/history \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"page":1,"count":20,"search":"acme","includeApi":true}'

Sample response

{
  "results": {
    "page": 1,
    "count": 20,
    "total": 143,
    "lastPage": 8,
    "direction": "DESC",
    "items": [
      {
        "id": "BG5CF5Z2q0SwIBmhZylJggxp",
        "userName": "ERP integration",
        "customerName": "Acme Widgets Inc",
        "request": {
          "name": "ACME WIDGETS INC",
          "requestedServices": "irs-tin-name-matching,list-sanctions"
        },
        "requestedOn": "2026-10-01T14:02:11Z",
        "completedOn": "2026-10-01T14:02:12Z",
        "requestState": 2,
        "irsResultType": 3,
        "listResultType": 3
      }
    ]
  }
}

Errors

Requests that cannot be processed return HTTP 400 with an object keyed by field name, each listing what was wrong. Authentication, permission and other status codes are covered in Errors & service status.

This endpoint requires an API key with the History permission.