Skip to main content
POST
TIN

Authorizations

Authorization
string
header
required

Use your API token as a Bearer token in the Authorization header.

Headers

Authorization
string
required
Example:

"Bearer {your_api_token}"

Accept
string
default:application/json
Content-Type
string
default:application/json

Body

application/json
tin
string
required

Nine-digit TIN.

Pattern: ^\d{9}$
Example:

"123456789"

branchCode
string
required

Five-digit branch code.

Pattern: ^\d{5}$
Example:

"00001"

firstName
string
required

First name.

Maximum string length: 100
Example:

"Jordan"

lastName
string
required

Last name.

Maximum string length: 100
Example:

"Santos"

genderDescription
enum<string>
required

Gender description.

Available options:
Male,
Female,
male,
female
birthDate
string<date>
required

Date of birth in YYYY-MM-DD format.

Example:

"1990-02-01"

middleName
string | null

Middle name.

Maximum string length: 100
Example:

"Dela"

suffixDescription
string | null

Name suffix, when applicable.

Maximum string length: 20
Example:

"Jr."

metadata
object

Optional key-value pairs echoed back in completed and source-error responses.

Response

Request processed. Check data.isValid and verificationStatus to determine the outcome.

success
boolean
required
Example:

true

message
string
required
data
object
required

CamelCase result fields for this verification type. Additional source fields may be returned when available.

verificationStatus
enum<string>
required
Available options:
VERIFIED,
REJECTED
verificationStatusCode
enum<integer>
required

3 = Verified, 1 = Rejected.

Available options:
3,
1
transactionId
string<uuid>
required
verificationType
string
required
Example:

"philippines_tin"

createdAt
string
required
Example:

"2026-09-01 08:00:00+0000"

metadata
object | null