Philippines NBI Clearance sandbox

Sandbox payloads for the Stateless NBI Clearance endpoint.

POST /api/v3/verifications/philippines/nbi-passthrough

When your account is in sandbox mode, these payloads return the outcomes shown below. Any other valid payload is answered as a no-match — HTTP 200 with isValid set to false. Values are case-sensitive. transactionId and createdAt are generated per request, and metadata is echoed back from your request. See Sandbox introduction for the full matching rules.

In live mode clearanceNo is upper-cased before it is sent to the NBI source. Sandbox matching runs on the value exactly as you send it, so nbisandbox-0000001 does not match NBISANDBOX-0000001 and is answered as a no-match.

Verified

VERIFIED — Clearance found and current

Request

{
  "clearanceNo": "NBISANDBOX-0000001"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines NBI Clearance processed successfully",
  "data": {
    "clearanceExpiry": "2027-07-23",
    "clearanceNumber": "NBISANDBOX-0000001",
    "lastname": "SANTOS",
    "firstname": "JORDAN",
    "isValid": true
  },
  "verificationStatus": "VERIFIED",
  "verificationStatusCode": 3,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_nbi_clearance",
  "createdAt": "<UTC timestamp of the request>"
}

clearanceExpiry is always returned as yyyy-mm-dd.

VERIFIED — Clearance found and current, with middle name

Request

{
  "clearanceNo": "NBISANDBOX-0000002"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines NBI Clearance processed successfully",
  "data": {
    "clearanceExpiry": "2028-03-15",
    "clearanceNumber": "NBISANDBOX-0000002",
    "lastname": "DELA CRUZ",
    "firstname": "MARIA",
    "middlename": "REYES",
    "isValid": true
  },
  "verificationStatus": "VERIFIED",
  "verificationStatusCode": 3,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_nbi_clearance",
  "createdAt": "<UTC timestamp of the request>"
}

middlename is only present when the clearance holder has one. Treat it as optional.

Rejected

A rejection is a completed verification, not an error: success is true and HTTP status is 200. In live mode a rejection is billed.

REJECTED — Clearance found but expired

Request

{
  "clearanceNo": "NBISANDBOX-0000003"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines NBI Clearance processed successfully",
  "data": {
    "clearanceExpiry": "2024-01-10",
    "clearanceNumber": "NBISANDBOX-0000003",
    "lastname": "GARCIA",
    "firstname": "PAOLO",
    "isValid": false
  },
  "verificationStatus": "REJECTED",
  "verificationStatusCode": 1,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_nbi_clearance",
  "createdAt": "<UTC timestamp of the request>"
}

The clearance exists, so the holder’s details are still returned, but it is no longer current. Do not treat the presence of lastname or clearanceNumber as a pass — branch on isValid or verificationStatus.

REJECTED — Clearance found but expired, with middle name

Request

{
  "clearanceNo": "NBISANDBOX-0000004"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines NBI Clearance processed successfully",
  "data": {
    "clearanceExpiry": "2025-06-30",
    "clearanceNumber": "NBISANDBOX-0000004",
    "lastname": "BAUTISTA",
    "firstname": "ANA",
    "middlename": "LIM",
    "isValid": false
  },
  "verificationStatus": "REJECTED",
  "verificationStatusCode": 1,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_nbi_clearance",
  "createdAt": "<UTC timestamp of the request>"
}

REJECTED — Clearance not found

Request

{
  "clearanceNo": "NBISANDBOX-0000005"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines NBI Clearance processed successfully",
  "data": {
    "isValid": false
  },
  "verificationStatus": "REJECTED",
  "verificationStatusCode": 1,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_nbi_clearance",
  "createdAt": "<UTC timestamp of the request>"
}

No record exists for this clearance number, so only isValid is returned.

REJECTED — Not found, unmatched payload fallback

Request

{
  "clearanceNo": "NBISANDBOX-0000006"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines NBI Clearance processed successfully",
  "data": {
    "isValid": false
  },
  "verificationStatus": "REJECTED",
  "verificationStatusCode": 1,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_nbi_clearance",
  "createdAt": "<UTC timestamp of the request>"
}

This clearance number matches no documented scenario, so it takes the no-match fallback — identical to the not-found rejection above apart from transactionId and metadata. Fire it once to confirm that an unknown clearance never reaches the live NBI source.

Validation failures

All validation failures return HTTP 400 with code set to VALIDATION_FAILED and the same message; only errors differs. Validation runs before any fixture matching, so these behave identically in sandbox and live. transactionId is null and no transaction row is written.

VALIDATION_FAILED — Clearance number missing

Request

{
  "clearanceNo": ""
}

Response — HTTP 400

{
  "success": false,
  "code": "VALIDATION_FAILED",
  "message": "The request could not be validated. Please check the submitted fields.",
  "errors": {
    "clearanceNo": ["The clearance no field is required."]
  },
  "transactionId": null,
  "verificationType": "philippines_nbi_clearance",
  "createdAt": "<UTC timestamp of the request>"
}

VALIDATION_FAILED — Clearance number not a string

Request

{
  "clearanceNo": 123456
}

Response — HTTP 400

{
  "success": false,
  "code": "VALIDATION_FAILED",
  "message": "The request could not be validated. Please check the submitted fields.",
  "errors": {
    "clearanceNo": ["The clearance no must be a string."]
  },
  "transactionId": null,
  "verificationType": "philippines_nbi_clearance",
  "createdAt": "<UTC timestamp of the request>"
}

VALIDATION_FAILED — Trust flow fields sent to a stateless endpoint

Request

{
  "clearanceNo": "NBISANDBOX-0000001",
  "trustFlowId": "anything"
}

Response — HTTP 400

{
  "success": false,
  "code": "VALIDATION_FAILED",
  "message": "The request could not be validated. Please check the submitted fields.",
  "errors": {
    "trustFlowId": ["The trust flow id field is prohibited."]
  },
  "transactionId": null,
  "verificationType": "philippines_nbi_clearance",
  "createdAt": "<UTC timestamp of the request>"
}

trustFlowId and trustValidationId are prohibited on stateless endpoints. Sending either is a validation failure, not a silently ignored field.

Source unavailable

FAILED — NBI source unavailable

Request

{
  "clearanceNo": "NBISANDBOX-0000009"
}

Response — HTTP 500

{
  "success": false,
  "code": "PH_GOV_UNAVAILABLE",
  "message": "The Philippine government source is currently unavailable. Please try again later.",
  "verificationStatus": "FAILED",
  "verificationStatusCode": 6,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_nbi_clearance",
  "createdAt": "<UTC timestamp of the request>"
}

There is no data key at all. The envelope treats code and data as mutually exclusive, so a coded failure drops data rather than emitting an empty object. Branch on code, not on the presence of data.

Account-level responses

Two further responses are not specific to this endpoint. A missing or invalid Authorization header returns HTTP 401, and an account without the philippines_nbi_clearance plan returns HTTP 403 — both enforced in sandbox exactly as in live. See Sandbox introduction for their envelopes.

Stateless API Sandbox

Australia DVS

Philippines Government

Document OCR

Verified

Rejected

Validation failures

Source unavailable

Account-level responses

​Verified

​Rejected

​Validation failures

​Source unavailable

​Account-level responses

Verified

Rejected

Validation failures

Source unavailable

Account-level responses