Include stakeholders

You can include related parties (stakeholders) when submitting entity verifications. Stakeholders represent individuals or companies associated with an entity, such as trustees, beneficiaries, or directors.

Stakeholder object structure

Each stakeholder in the stakeholders array must include:

Field	Type	Required	Description
`role`	string	Yes	The stakeholder's role (e.g., `trustee`, `beneficiary`).
`type`	string	Yes	Entity type (`individual`, `company`, `trust`, etc.).
`subType`	string	No	Entity sub-type (e.g., `discretionaryTrust`, `none`).
`country`	string	Yes	ISO3 country code.
`name`	string	Yes	Entity name or full name for individuals.
`identifiers`	object	No	Entity identifiers (ABN, ACN, etc.).
`addresses`	object	No	Entity addresses.

The stakeholder object follows the same field structure as the main entity, with type, country, name, and relevant identifiers at the same level as role.

Required stakeholders

Some entity types have required stakeholders, and the available roles vary by entity type. For example, a trust requires at least one trustee. If you submit a verification without the required stakeholder, you'll receive a validation error.

Validation error

{
  "timestamp": "2026-01-30T02:42:22.799Z",
  "serviceUid": "5qA5Hq0n1JQTY2TASItxYXSRyND3",
  "trace": "1NZi6cI13qdpce3F1B7wB",
  "path": "/v5/verifications",
  "statusCode": 422,
  "message": "Validation error",
  "help": null,
  "status": "error",
  "data": null,
  "error": {
    "type": "validation_error",
    "details": [
      {
        "message": "All required stakeholder roles must be filled",
        "code": "custom",
        "path": ["stakeholders"]
      }
    ]
  }
}

POST/v5/verifications

Example: Australian trust

In this example, we will create a verification for an Australian discretionary trust. The trustee stakeholder role is required for trusts, and we'll include a corporate trustee.

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
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 (ABN required for Australian trusts)
Name
addresses
Type
object
Description
Entity addresses
Name
documents
Type
array
Description
Array of document objects (trustDeed required for trusts)
Name
stakeholders
Type
array
Description
Array of stakeholder objects (trustee required for trusts)

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": "trust",
      "subType": "discretionaryTrust",
      "name": "Smith Family Trust",
      "industry": "Investment",
      "website": "https://smithfamilytrust.com.au",
      "inputRisk": "low",
      "identifiers": {
        "abn": "12345678901"
      },
      "addresses": {},
      "documents": [
        {
          "kind": "trustDeed",
          "mimeType": "image/png",
          "source": "base64",
          "data": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAUAAAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO9TXL0Y4OHwAAAABJRU5ErkJggg==",
          "fileName": "trust-deed.png"
        }
      ],
      "stakeholders": [
        {
          "role": "trustee",
          "type": "company",
          "subType": "none",
          "country": "AUS",
          "name": "Smith Trustee Pty Ltd",
          "industry": "Trustee Services",
          "website": "https://smithtrustee.com.au",
          "identifiers": {
            "acn": "123456789",
            "abn": "98765432101"
          },
          "addresses": {
            "registeredAddress": "Level 5, 100 Collins St, Melbourne VIC 3000",
            "principalPlaceOfBusiness": "Suite 10, 50 Bridge St, Sydney NSW 2000"
          }
        }
      ]
  }'

Response

{
  "timestamp": "2026-01-30T02:45: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?

Great, you've now learned how to include addresses, documents, and stakeholders in your verification requests. Next, learn how to control test outcomes using test keywords in the Preview environment.