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.
| Outcome | Parameter | Value |
|---|---|---|
| Verified | middleName | ok |
| Verified with positive watchlist matches | middleName | pep |
Australia-specific test values
For Australian individual verifications, you can use these document numbers to get verified responses:
| Outcome | Parameter | Value |
|---|---|---|
| Verified driver licence | driverLicenceNumber | 11111111 |
| Verified passport | passportNumber | A1111111 |
| Verified medicare | medicareCardNumber | 2111111111 |
Entities
You can use the name parameter to trigger different verification results when submitting entities. The verification status change (after the initial pending response) will be sent to your registered webhook.
| Outcome | Parameter | Value |
|---|---|---|
| Verified | name | Starts with Pass |
| Verified with positive watchlist matches | name | Starts with Pass PEP |
| Info | name | Starts with Info |
| Rejected | name | Starts with Fail |
Watchlist screening
You can include a keyword anywhere in the entity name to control the screening outcome:
| Keyword | Screening result |
|---|---|
sanction | Returns a sanctions list hit |
pep | Returns a PEP (politically exposed person) hit |
criminal | Returns a criminal record hit |
multi | Returns sanctions + PEP hits |
| (none) | Clear — no hits |
For example, "Pass Sanction Corp Pty Ltd" will produce a verified entity with a sanctions hit.
See Watchlist 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 entity
Use a name starting with Pass to trigger a verified status.
Request body:
{
"userId": "test-verified-entity",
"country": "AUS",
"type": "company",
"subType": "none",
"name": "Pass My Company Pty Ltd",
"industry": "Test Industry",
"website": "https://example.com",
"inputRisk": "unknown",
"identifiers": { "acn": "123456789" },
"addresses": {},
"stakeholders": [],
"documents": []
}
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-entity","country":"AUS","type":"company","subType":"none","name":"Pass My Company Pty Ltd","industry":"Test Industry","website":"https://example.com","inputRisk":"unknown","identifiers":{"acn":"123456789"},"addresses":{},"stakeholders":[],"documents":[]}'
Info status (additional information required)
Use a name starting with Info to trigger an info status, which indicates additional information is required.
Request body:
{
"userId": "test-info-entity",
"country": "AUS",
"type": "company",
"subType": "none",
"name": "Info My Company Pty Ltd",
"industry": "Test Industry",
"website": "https://example.com",
"inputRisk": "unknown",
"identifiers": { "acn": "123456789" },
"addresses": {},
"stakeholders": [],
"documents": []
}
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-info-entity","country":"AUS","type":"company","subType":"none","name":"Info My Company Pty Ltd","industry":"Test Industry","website":"https://example.com","inputRisk":"unknown","identifiers":{"acn":"123456789"},"addresses":{},"stakeholders":[],"documents":[]}'
Rejected entity
Use a name starting with Fail to trigger a rejected status.
Request body:
{
"userId": "test-rejected-entity",
"country": "AUS",
"type": "company",
"subType": "none",
"name": "Fail My Company Pty Ltd",
"industry": "Test Industry",
"website": "https://example.com",
"inputRisk": "unknown",
"identifiers": { "acn": "123456789" },
"addresses": {},
"stakeholders": [],
"documents": []
}
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-entity","country":"AUS","type":"company","subType":"none","name":"Fail My Company Pty Ltd","industry":"Test Industry","website":"https://example.com","inputRisk":"unknown","identifiers":{"acn":"123456789"},"addresses":{},"stakeholders":[],"documents":[]}'
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"}'
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