TIN Verification

post

https://verify.vouched.id/api/tin/verify

TIN Verification job.

Requires the tinValidationEnabled account feature; without it the request is rejected with a 403 AccountConfigErrorType.

Test mode is not supported for this endpoint. Unlike POST /api/ssn, the x-test-request header is read but unimplemented here, and sending x-test-request: true fails with a 500 UnknownSystemError. Do not send it.

When the result cannot be determined synchronously the response comes back with status: pending and result.status: PENDING; the final result arrives at your callbackURL and is also readable from GET /api/tin/jobs/{id} once status is complete.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

📘
Accented and diacritic characters are supported.
Vouched automatically normalizes name fields before verification. Note that the TIN endpoint accepts only letters, digits, spaces, hyphens, and &; other punctuation (such as apostrophes in A'rreion) is replaced with a space before matching.

Body Params

firstName

string

required

length ≥ 1

First name linked to the TIN number in the request. The first 40 characters of the combined first and last names are used in the matching process. Must only contain letters, spaces, hyphens, and ampersands.

lastName

string

required

length ≥ 1

Last name linked to the TIN number in the request. The first 40 characters of the combined first and last names are used in the matching process. Must only contain letters, spaces, hyphens, and ampersands.

tinType

string

enum

required

ITIN

Allowed:

tin

string

required

The full 9 digits of the TIN in the request. Do not include dashes or spaces.

callbackURL

string

required

Upon completion of a pending job, Vouched will POST the job results to the defined webhook.

phone

string

required

The phone number of the individual for this request. Formatted in E.164 formatting for international numbers including the leading plus sign. For example +12065551111

Responses

200Success

400InvalidRequestError - The request is invalid. An aborted or oversized request is answered with this status and an empty body instead of the envelope below.

401The request could not be authenticated. Credential rejection returns an AuthenticationError envelope; a malformed or expired bearer token is rejected earlier by the JWT middleware and returns { "error": "Token expired" } or { "error": "Token malformed" } instead.

403AccountConfigErrorType - The feature is not enabled for this account. SSN operations return SSNAccountConfigErrorType instead and document their own 403.

500UnknownSystemError - A unknown system error occurred.