Skip to main content
POST

Sandbox testing

Use sandbox mode with predetermined API payloads to retrieve every status this endpoint can return. Each payload is mapped to a specific outcome so you can confirm how your integration handles verified results.

Philippines NDRP sandbox payloads

Predetermined request and response examples for every returned status.

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
fullName
string
required

Full name to search. This is the only value sent to NDRP.

Required string length: 2 - 255
Example:

"Pedro Santos Garcia"

dateOfBirth
string<date>

Optional birth date in YYYY-MM-DD format. Not sent to NDRP; compared with the birth dates of the records NDRP returns. An exact match rejects the check.

Example:

"1980-03-10"

restrictedMatchAction
enum<string>
default:manual

Status to use when NDRP returns a record but no birth date matches. manual returns REVIEW_NEEDED; rejected returns REJECTED.

Available options:
manual,
rejected
metadata
object

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

Response

Request processed. Check verificationStatus to determine the outcome. A restricted match is still HTTP 200.

success
boolean
required
Example:

true

message
string
required
data
object
required

NDRP search result. birthdate and photoPath are null when NDRP has no value.

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

3 = Verified, 2 = Review needed, 1 = Rejected.

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

"philippines_ndrp"

createdAt
string
required
Example:

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

metadata
object | null