Banned Person

Information about people that ASIC has disqualified or banned. People that have been: disqualified from involvement in the management of a corporation, disqualified from auditing self-managed superannuation funds (SMSFs) and banned from practising in the Australian financial services (AFS) or credit industry.

Information provided in this search is taken from the following registers: disqualified persons register, credit banned/disqualified [persons] register, AFS banned/disqualified persons register

More about Banned Organisation on ASIC website →

Model

Specific structure of the data that represents the entity within the API. It defines the attributes and their data types associated with the entity.

It's important to note that you'll need to retrieve the complete identifier for an entity each time you require its complete model. This can be achieved by utilizing the find endpoint to locate the entity and then using the retrieved identifier to call the retrieve endpoint for complete model.

This API prioritizes efficient data transmission and minimizes response sizes. While the retrieve endpoint provides the complete data model for a requested entity, it adheres to the principle of "sparse representation." This means that certain properties within the model might be omitted if they lack any relevant data for the specific entity.

  • Name
    id
    Type
    string
  • Name
    name
    Type
    string
  • Name
    address
    Type
    object
    Description
    • Name
      locality
      Type
      string
    • Name
      state
      Type
      string
    • Name
      postcode
      Type
      string
    • Name
      country
      Type
      string
  • Name
    reason
    Type
    string
  • Name
    docNumber
    Type
    string
  • Name
    comment
    Type
    string
  • Name
    dateFrom
    Type
    string
  • Name
    dateTo
    Type
    string
  • Name
    isPermanent
    Type
    boolean
GET/asic/banned/person/find/

Find

This API endpoint utilizes a full-text search functionality to help you locate entities that match with your search criteria. By providing a query, system will scan through all available data, pinpointing all entities that contain relevant keywords or phrases.

The find endpoint performs full-text search across the following field: name.

This API endpoint prioritizes speed and efficiency by returning a partial model with a limited set of properties for each matching entity. To retrieve the complete entity details, you can leverage retrieve API endpoint designed for specific entity retrieval based on unique identifiers.

Mandatory headers

  • Name
    x-api-key
    Type
    string
    Description
    A valid API key obtained through active subscription must be included in the header in order for the endpoint to work.

Mandatory attributes

  • Name
    query
    Type
    string
    Description
    This mandatory attribute represents the search query you wish to execute. The query string must be at least three characters long for the search to function effectively.

Optional attributes

  • Name
    offset
    Type
    integer
    Description
    Pagination is implemented to manage potentially large result sets. This optional parameter allows you to specify the number of entities to skip before retrieving the desired page of results.

Request

GET
/asic/banned/person/find/
curl "https://api.vigil.sh/asic/banned/person/find/?query={query}" \
  -H 'x-api-key: {api-key}'

Response

{
  "results": [
    {
      "id": "46yuvG1bc2ZWh13rwhzGwLMuUy1N3YMK8Q==",
      "name": "TERRA AUSTRALIS"
    },
    // ...
  ],
  "resultsTotal": 565
}
GET/asic/banned/person/

Retrieve

This API endpoint utilizes a data retrieval functionality to help you access the entity associated with a provided unique identifier. When you provide a unique identifier, the system scans through all available data in order to pinpoint the exact entity that matches that identifier.

This API endpoint prioritizes the integrity and comprehensiveness of your data by returning the complete data model with the entire set of properties for the matching entity. To find the different entity, you can leverage find API endpoint designed for full-text search based on your query.

Mandatory headers

  • Name
    x-api-key
    Type
    string
    Description
    A valid API key obtained through active subscription must be included in the header in order for the endpoint to work.

Mandatory attributes

  • Name
    id
    Type
    string
    Description
    This mandatory attribute represents the unique identifier associated with specific entity. The unique identifiers used within this API are not static values. Instead, they employ a rotation mechanism, meaning they change frequently, often with nearly every request.

Request

GET
/asic/banned/person/
curl "https://api.vigil.sh/asic/banned/person/?id={id}" \
  -H 'x-api-key: {api-key}'

Response

{
  "name": "TERRA AUSTRALIS",
  "address": {
    "locality": "SYDNEY",
    "state": "NSW",
    "postcode": "2000",
    "country": "AUSTRALIA"
  },
  "reason": "Banned Securities",
  "docNumber": "#123456789",
  "dateFrom": "01/01/2000",
  "dateTo": "01/01/2099"
}