ASIC Insolvency Notices API Reference
This is the ASIC insolvency notices API behind the product: a REST API that collects notices published by the Australian Securities & Investments Commission (ASIC) and lets you search them, watch companies over time, and get alerted when one enters liquidation, administration or restructuring.
Getting an API key
Section titled “Getting an API key”Every request except GET /health needs an API key. You get one by subscribing to a plan, and every plan starts with a 7 day free trial.
- Pick a plan on the pricing page and complete checkout.
- The page you land on after checkout shows your API key. It is shown once and stored only as a hash, so we can’t recover it later. Copy it into your password manager or secrets store before you leave the page.
- On the same page, create a login for your dashboard.
Lost your key, or think it has been exposed? Sign in to the dashboard, open API & webhooks and choose Generate a new key. The new key is shown once, and the old one stops working straight away.
Getting started covers how to send the key with each request.
Base URL
Section titled “Base URL”https://api.insolvencyalerts.com.auEvery example in these docs uses this host.
Where the data comes from
Section titled “Where the data comes from”A collector reads ASIC’s published-notices sitemap and loads each new notice page, continuously. ASIC’s sitemap runs about a day behind, so a notice typically appears in the API within a day of ASIC publishing it.
The archive reaches back 365 days, and nothing is ever deleted, so it only grows from there. The initial backfill is still working through the oldest part of that window: GET /health reports the range covered right now as notices.oldest and notices.newest, and needs no key.
Every notice result includes source_url, a link back to the original ASIC notice. If you show notice data to your own users, keep that link alongside it.
What you can do
Section titled “What you can do”- Search notices: full-text company search, plus filters on state, appointment type, notice type and date.
- Watch companies: give the API a list of ACNs or ABNs and poll or subscribe for matches.
- Get webhooks: have matches pushed to your own endpoint instead of polling.
- Handle errors: every code the API returns, and which are worth retrying.
Start with Getting started for authentication and your first request.