Test values

You can use these test values to trigger different verification outcomes when testing your integration in the Preview environment.

Individuals

To get a verified response for an individual, you can use the middleName parameter, or you can submit 2 verified ID documents. Any other values will result in a rejected verification.

The middle name is the only field checked for test keywords, so the first and last name stay free for realistic test data. There is no rejection keyword — synthetic identities don't match any real data source in Preview, so any submission without a verified keyword is rejected.

Australia-specific test values

For Australian individual verifications, you can use these document numbers to get verified responses:

Entities

For entity (KYB) verifications, the start of the entity's name carries the test keyword.

A name starting with info simulates the automated information-request flow: a sample stakeholder and a sample document are requested, and the verification then transitions to info status. A name without a keyword prefix returns pending and progresses as the requested documents and stakeholders are completed; status changes are sent to your registered webhook.

You can also control the screening outcome for an entity by including a screening keyword anywhere in the name parameter — see Screening below.

Screening

Screening keywords control the screening outcome in the Preview environment:

• Individuals — include the keyword in the middleName parameter, combined with a verified keyword so the verification passes first (for example "middleName": "ok sanction"). The keyword pep on its own both verifies the individual and produces a PEP hit.
• Entities — include the keyword anywhere in the name parameter.

See Watchlist Screening and Negative Media Screening for the endpoint documentation.

Code samples

The examples below show how to trigger each verification outcome. Replace the credentials with your own API keys.

Verified individual

Use middleName: "ok" to trigger a verified status for an individual.

Request body:

{
	"userId": "test-verified-individual",
	"country": "AUS",
	"type": "individual",
	"subType": "none",
	"firstName": "John",
	"middleName": "ok",
	"lastName": "Smith",
	"email": "john.smith@example.com",
	"dateOfBirth": "1990-01-15"
}

cURL example:

curl -X POST https://dev.bronid.com/v5/verifications \
  --user "your-api-key:your-api-secret" \
  -H "Content-Type: application/json" \
  --data '{"userId":"test-verified-individual","country":"AUS","type":"individual","subType":"none","firstName":"John","middleName":"ok","lastName":"Smith","email":"john.smith@example.com","dateOfBirth":"1990-01-15"}'

Verified individual with a sanctions hit

Combine a verified keyword with a screening keyword in the middle name to verify the individual and produce a watchlist hit.

Request body:

{
	"userId": "test-sanctioned-individual",
	"country": "AUS",
	"type": "individual",
	"subType": "none",
	"firstName": "John",
	"middleName": "ok sanction",
	"lastName": "Smith",
	"email": "john.smith@example.com",
	"dateOfBirth": "1990-01-15"
}

cURL example:

curl -X POST https://dev.bronid.com/v5/verifications \
  --user "your-api-key:your-api-secret" \
  -H "Content-Type: application/json" \
  --data '{"userId":"test-sanctioned-individual","country":"AUS","type":"individual","subType":"none","firstName":"John","middleName":"ok sanction","lastName":"Smith","email":"john.smith@example.com","dateOfBirth":"1990-01-15"}'

Rejected individual

Submit an individual without a verified keyword in the middle name. The synthetic identity won't match any real data source in Preview, so the verification is rejected.

Request body:

{
	"userId": "test-rejected-individual",
	"country": "AUS",
	"type": "individual",
	"subType": "none",
	"firstName": "John",
	"middleName": "James",
	"lastName": "Smith",
	"email": "john.smith@example.com",
	"dateOfBirth": "1990-01-15"
}

cURL example:

curl -X POST https://dev.bronid.com/v5/verifications \
  --user "your-api-key:your-api-secret" \
  -H "Content-Type: application/json" \
  --data '{"userId":"test-rejected-individual","country":"AUS","type":"individual","subType":"none","firstName":"John","middleName":"James","lastName":"Smith","email":"john.smith@example.com","dateOfBirth":"1990-01-15"}'

What's next?

• Set up webhooks to receive verification status updates
• Learn about verification statuses and how to retrieve detailed results
• Handle errors that may occur during verification