Entity Lookup

Use the /entity-lookup endpoint to search for an entity by its registry identifier and retrieve basic information such as the entity name, status, classification, and address. This is useful for pre-filling verification or form submissions with official registry data before calling the Forms API or KYB API.

Supported countries

Look up an entity

curl "https://dev.bronid.com/v5/entity-lookup?country=AUS&id=33051775556" \
  --user "XL7ULiU6B4QE9Y2iWFZnhtMDKFN2:api_sec_NJAtNcRtUrPlf7xYDrMNP9URI-ZfN314"

{
  "timestamp": "2026-07-10T04:34:37.668Z",
  "serviceUid": "XL7ULiU6B4QE9Y2iWFZnhtMDKFN2",
  "trace": "V1StGXR8_Z5jdHi6B-myT",
  "path": "/v5/entity-lookup",
  "pathParams": {},
  "statusCode": 200,
  "message": "Entity found.",
  "help": null,
  "status": "success",
  "error": null,
  "data": {
    "country": "AUS",
    "name": "TELSTRA CORPORATION LIMITED",
    "classification": {
      "default": {
        "type": "company",
        "subType": "none",
        "description": "Australian Public Company"
      },
      "options": [
        {
          "type": "company",
          "subType": "none",
          "description": "Australian Public Company"
        }
      ]
    },
    "identifiers": {
      "abn": "33051775556",
      "acn": "051775556"
    },
    "names": [
      {
        "value": "TELSTRA INFRACO",
        "type": "businessName"
      },
      {
        "value": "TELSTRA",
        "type": "tradingName"
      }
    ],
    "entityStatus": "Active",
    "address": {
      "text": "VIC 3000",
      "state": "VIC",
      "postcode": "3000"
    },
    "dateRegistered": "1999-11-01"
  }
}

{
  "timestamp": "2026-07-10T04:34:37.668Z",
  "serviceUid": "XL7ULiU6B4QE9Y2iWFZnhtMDKFN2",
  "trace": "V1StGXR8_Z5jdHi6B-myT",
  "path": "/v5/entity-lookup",
  "pathParams": {},
  "statusCode": 200,
  "message": "Entity found.",
  "help": null,
  "status": "success",
  "error": null,
  "data": {
    "country": "NZL",
    "name": "SPARK NEW ZEALAND LIMITED",
    "classification": {
      "default": {
        "type": "company",
        "subType": "none",
        "description": "NZ Limited Company"
      },
      "options": [
        {
          "type": "company",
          "subType": "none",
          "description": "NZ Limited Company"
        }
      ]
    },
    "identifiers": {
      "nzbn": "9429039661098",
      "nzcn": "303826"
    },
    "names": [
      {
        "value": "SPARK NEW ZEALAND",
        "type": "tradingName"
      }
    ],
    "entityStatus": "Registered",
    "address": null,
    "dateRegistered": "1987-02-24"
  }
}

The entity lookup data model

A successful response carries the matched entity's registry information in the envelope's data field.

Properties

Names array

Identifiers object

All keys are optional — only the identifiers the registry holds for the entity are present.

Address object

Error responses

Errors follow the standard v5 error envelope — see Validation errors for the general format.

Entity not found

Returned with HTTP status 404 when the identifier does not match any entity in the registry.

{
	"timestamp": "2026-07-10T04:34:37.668Z",
	"serviceUid": "XL7ULiU6B4QE9Y2iWFZnhtMDKFN2",
	"trace": "V1StGXR8_Z5jdHi6B-myT",
	"path": "/v5/entity-lookup",
	"pathParams": {},
	"statusCode": 404,
	"status": "error",
	"message": "Not found",
	"help": null,
	"data": null,
	"error": {
		"type": "not_found",
		"details": [
			{
				"message": "No registry match found for the provided identifier.",
				"code": "not_found",
				"path": ["id"]
			}
		]
	}
}

Unsupported country or invalid parameters

Returned with HTTP status 422 when the country parameter is not a supported country, or when required parameters are missing or invalid. An id that fails its country's checksum (a valid ABN/ACN for AUS, a valid NZBN or a 1-7 digit NZCN for NZL) is rejected here rather than reaching the registry — a malformed identifier is a client error, not a 404 or a retryable 503.

{
	"timestamp": "2026-07-10T04:34:37.668Z",
	"serviceUid": "XL7ULiU6B4QE9Y2iWFZnhtMDKFN2",
	"trace": "V1StGXR8_Z5jdHi6B-myT",
	"path": "/v5/entity-lookup",
	"pathParams": {},
	"statusCode": 422,
	"status": "error",
	"message": "Validation error",
	"help": null,
	"data": null,
	"error": {
		"type": "validation_error",
		"details": [
			{
				"message": "Country not supported: GBR. Supported countries: AUS, NZL",
				"code": "validation_error",
				"path": ["country"]
			}
		]
	}
}

Registry unavailable

Returned with HTTP status 503 when the upstream business registry could not be reached (outage or network failure). This is distinct from a 404: the entity may well exist — retry the request later.

{
	"timestamp": "2026-07-10T04:34:37.668Z",
	"serviceUid": "XL7ULiU6B4QE9Y2iWFZnhtMDKFN2",
	"trace": "V1StGXR8_Z5jdHi6B-myT",
	"path": "/v5/entity-lookup",
	"pathParams": {},
	"statusCode": 503,
	"status": "error",
	"message": "Service unavailable",
	"help": null,
	"data": null,
	"error": {
		"type": "service_unavailable",
		"details": [
			{
				"message": "The business registry could not be reached. Try again later.",
				"code": "service_unavailable"
			}
		]
	}
}

Working With Classification

Use the classification field as your source of truth for choosing type and subType values for downstream API calls.

1) Classification Schema

2) Classification Item Schema

Both default and every options entry use this shape.

3) How To Use It

1. Call /v5/entity-lookup and read data.classification.options.
2. If options has exactly 1 pair — the entity classification is unambiguous. Auto-select classification.default and skip any user prompt.
3. If options has multiple pairs — the registry entity type is ambiguous (e.g. a Government Co-operative could be cooperative, governmentBody, or other, and a trust code can allow several trust subtypes). Pre-select classification.default but let the customer choose from all options.
4. Submit the selected type and subType values directly to the Forms API or KYB API.

4) Practical Examples

Example A — Unambiguous entity (auto-select)

An Australian Private Company (ABN lookup). A single option pair. Use the default directly — no user selection needed.

{
	"classification": {
		"default": { "type": "company", "subType": "none", "description": "Australian Private Company" },
		"options": [{ "type": "company", "subType": "none", "description": "Australian Private Company" }]
	}
}

Auto-populate type: "company" and subType: "none" in your form submission.

Example B — Ambiguous entity type (let user choose type)

A Government Co-operative registered with ABR. The registry code maps to 3 possible types. Pre-select the default but present all options to the customer.

{
	"classification": {
		"default": { "type": "cooperative", "subType": "none", "description": "Government Co-operative" },
		"options": [
			{ "type": "cooperative", "subType": "none", "description": "Government Co-operative" },
			{ "type": "governmentBody", "subType": "none", "description": "Government Co-operative" },
			{ "type": "other", "subType": "none", "description": "Government Co-operative" }
		]
	}
}

Show a selector pre-filled with "cooperative". The customer can confirm or switch to "governmentBody" or "other".

Example C — Known type, multiple subtypes (let user choose subtype)

A trust registered with the NZBN. The type is known (trust) but the specific trust subtype is ambiguous.

{
	"classification": {
		"default": { "type": "trust", "subType": "discretionaryTrust", "description": "Trading trusts" },
		"options": [
			{ "type": "trust", "subType": "discretionaryTrust", "description": "Trading trusts" },
			{ "type": "trust", "subType": "unitTrust", "description": "Trading trusts" },
			{ "type": "trust", "subType": "hybridTrust", "description": "Trading trusts" }
		]
	}
}

Show a subtype selector pre-filled with "discretionaryTrust". The customer can confirm or pick "unitTrust" or "hybridTrust".

What's next?

Once you have the lookup response, use the classification values to pre-fill your downstream API requests:

• Use classification to pre-fill a Forms API request
• Use classification to submit a KYB API request