Philippines National Police sandbox

Sandbox payloads for the Stateless National Police endpoint.

POST /api/v3/verifications/philippines/national-police-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.

Both clearanceNo and surname must match a documented scenario exactly, including case. Santos matches the verified scenario below; SANTOS and santos do not, and are answered as a no-match.

Verified

VERIFIED — Clearance and surname match

Request

{
  "clearanceNo": "TRASB120260101000001",
  "surname": "Santos"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines National Police processed successfully",
  "data": {
    "surname": "SANTOS",
    "fullname": "SANTOS, JORDAN DELA",
    "hitVerificationId": 1,
    "isValid": true,
    "clearanceNumber": "TRASB120260101000001"
  },
  "verificationStatus": "VERIFIED",
  "verificationStatusCode": 3,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_national_police",
  "createdAt": "<UTC timestamp of the request>"
}

VERIFIED — Clearance and compound surname match

Request

{
  "clearanceNo": "TRASB120260101000002",
  "surname": "Dela Cruz"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines National Police processed successfully",
  "data": {
    "surname": "DELA CRUZ",
    "fullname": "DELA CRUZ, MARIA REYES",
    "hitVerificationId": 1,
    "isValid": true,
    "clearanceNumber": "TRASB120260101000002"
  },
  "verificationStatus": "VERIFIED",
  "verificationStatusCode": 3,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_national_police",
  "createdAt": "<UTC timestamp of the request>"
}

Send multi-word surnames with their spaces, exactly as printed on the clearance.

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, surname does not match

Request

{
  "clearanceNo": "TRASB120260101000001",
  "surname": "Garcia"
}

Response — HTTP 200

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

REJECTED — Clearance not found

Request

{
  "clearanceNo": "TRASB120260101000005",
  "surname": "Bautista"
}

Response — HTTP 200

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

REJECTED — Not found, unmatched payload fallback

Request

{
  "clearanceNo": "TRASB120260101000006",
  "surname": "Santos"
}

Response — HTTP 200

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

This payload matches no documented scenario, so it takes the no-match fallback — identical to the rejections above apart from transactionId and metadata. Fire it once to confirm that an unknown clearance never reaches the live PNP 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": "",
  "surname": "Santos"
}

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_national_police",
  "createdAt": "<UTC timestamp of the request>"
}

VALIDATION_FAILED — Surname missing

Request

{
  "clearanceNo": "TRASB120260101000001"
}

Response — HTTP 400

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

VALIDATION_FAILED — Trust flow fields sent to a stateless endpoint

Request

{
  "clearanceNo": "TRASB120260101000001",
  "surname": "Santos",
  "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_national_police",
  "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 — PNP source unavailable

Request

{
  "clearanceNo": "TRASB120260101000009",
  "surname": "Santos"
}

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_national_police",
  "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-national-police 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

Philippines National Police sandbox

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