ASIC ID Check
/api/v2/asic_id_check
operationId: asic_id_check
Live: https://gdapi.globaldata.net.au/api/v2/asic_id_check · Sandbox: https://sandbox-gdapi.globaldata.net.au/api/v2/asic_id_check
Verifies a person against the ASIC officeholder and shareholder register using their name and date of birth.
Returns a small match_results summary indicating whether the supplied details match an ASIC record.
Use this endpoint when you need to confirm a person is on the ASIC register. If you need the actual ASIC
record (officeholdings, shareholdings, addresses, etc.) use /asic_extract_person_search and /asic_extract
instead.
Match rules
- First name, last name and
birth_datemust all match an ASIC record for the check to pass. middle_name, when supplied, is reported on but does not gate the result. A check can pass withmiddle_name: no_match. ASIC's middle-name records are inconsistent - it is common for them to be missing entirely, recorded as an initial only, or only partially recorded - so we treat the middle name as a soft signal rather than a hard requirement.
Name matching
Name comparisons are case-insensitive and use the following normalisation rules on both the supplied value and the ASIC record:
- Case.
Smith,SMITH, andsmithare treated as the same name. - Accents and non-ASCII characters. Transliterated to ASCII before comparison.
Mülleris treated asMuller,AndréasAndre. - Apostrophes. Ignored.
O'DonnellandODonnellare treated as the same name. Both straight (') and curly (’) apostrophes are normalised. - Hyphens. Significant.
Smith-JonesandSmith Jones(orSmithJones) are not treated as the same name - they should be supplied exactly as the ASIC record has them. - Punctuation and brackets. Dots and parenthesised content are stripped before comparison
(
John (Jack)is treated asJohn,St.asSt). - Whitespace. Repeated whitespace is collapsed to single spaces and leading/trailing whitespace is trimmed.
There is no fuzzy matching - all comparisons are exact after the normalisation rules above.
Input expectations
- Names should be provided as they appear on ASIC records. A combined maximum of three given names is
allowed across
first_nameandmiddle_name. birth_datemust be an ISOYYYY-MM-DDdate after 1900-01-01.
Response
The match_results object has two keys:
person:matchwhen the supplied first name, last name and date of birth match an ASIC record; otherwiseno_match.no_matchalso covers the case where the search criteria are too broad to evaluate against a single record.middle_name:matchwhen the supplied middle name matches the ASIC record,no_matchwhen it does not (or the ASIC record has no middle name on file), ornot_providedwhen no middle name was supplied.
Sandbox environment
The sandbox person register is deterministic. The name and date of birth combinations that pass an ID check are listed in the ASIC Sandbox Data guide.
Request body
Content type application/json.
Details of the individual to check.
| Field | Description |
|---|---|
first_namerequired |
string [max 100 characters] The person's first given name (one to three given names when combined with |
middle_name |
string [max 100 characters] or null Optional middle names. Combined with |
last_namerequired |
string [max 100 characters] The person's family name as recorded with ASIC. |
birth_daterequired |
string (date) The person's date of birth in |
Responses
ID check completed. The match_results object contains the verification outcome.
application/json
| Field | Description |
|---|---|
message |
string Always |
function |
string The API function that handled the request. |
api_reference |
string (uuid) Audit reference for this ID check. |
match_results |
object The verification outcome. Carries no PII. |
match_results. |
string
|
match_results. |
string
|