Control test outcomes

In the Preview environment, you can control the outcome of submitted verifications by using special keywords in the entity name. This allows you to test different scenarios without needing real data.

Test keywords only work in the Preview environment (dev.bronid.com). In production, verifications are processed using real data sources.

Test keywords

Use these keywords at the start of the entity name field to trigger different verification outcomes:

Keyword	Outcome
`Pass`	Results in a verified status.
`Pass PEP`	Results in a verified status with positive watchlist matches.
`Info`	Results in the system requesting additional information to complete the verification.
`Fail`	Results in a rejected status.

When you submit an entity verification in the Preview environment, the system checks if the entity name starts with one of the test keywords. If it does, the verification will be processed to produce the corresponding outcome.

For example:

"Pass My Company Pty Ltd" will result in a verified status
"Info My Company Pty Ltd" will result in the system requesting additional information
"Fail My Company Pty Ltd" will result in a rejected status

POST/v5/verifications

Example: Trigger a verified outcome

In this example, we submit an Australian company with a name starting with Pass to trigger a verified outcome.

Request body

Name
country
Type
string
Description
ISO3 Country code of the entity
Name
type
Type
string
Description
Entity type
Name
subType
Type
string
Description
Entity sub-type
Name
name
Type
string
Description
Entity name (starts with test keyword)
Name
industry
Type
string
Description
Industry description
Name
website
Type
string
Description
Entity website URL
Name
inputRisk
Type
string
Description
IDV Risk level of the entity
Name
identifiers
Type
object
Description
Entity identifiers
Name
addresses
Type
object
Description
Entity addresses
Name
documents
Type
array
Description
Array of document objects
Name
stakeholders
Type
array
Description
Array of stakeholder objects

Request

POST

/v5/verifications

curl https://dev.bronid.com/v5/verifications \
  --user "XL7ULiU6B4QE9Y2iWFZnhtMDKFN2:api_sec_NJAtNcRtUrPlf7xYDrMNP9URI-ZfN314" \
  --header "Content-Type: application/json" \
  --data '{
      "country": "AUS",
      "type": "company",
      "subType": "none",
      "name": "Pass My Company Pty Ltd",
      "industry": "Technology",
      "website": "https://mycompany.com.au",
      "inputRisk": "low",
      "identifiers": {
        "acn": "123456789"
      },
      "addresses": {},
      "documents": [],
      "stakeholders": []
  }'

Response

{
  "timestamp": "2026-01-30T03:00:42.101Z",
  "serviceUid": "XL7ULiU6B4QE9Y2iWFZnhtMDKFN2",
  "trace": "_mycHhuXA8vDMTgbCsqJf",
  "path": "/v5/verifications",
  "pathParams": {},
  "statusCode": 200,
  "message": "Verification created successfully",
  "help": null,
  "status": "success",
  "data": null,
  "error": null
}

What's next?

Now that you know how to control test outcomes, learn how to provide missing information for incomplete verifications.