Notices
Search notices
Section titled “Search notices”GET /v1/notices
| Param | Example | Notes |
|---|---|---|
q |
drifta stockton |
Company name, including former names and business names. Partial words work. A 9-digit number is treated as an ACN. |
acn |
643233676 or 643 233 676 |
|
appointment_type |
Court Liquidation |
Can repeat, or comma-separate. |
notice_purpose |
Appointment,Meeting |
|
notice_code |
465A(1)(c) |
Corporations Act / Regulations section, in the same form as ASIC’s “Notice” advanced-search dropdown. Can repeat, or comma-separate. |
state |
NSW,VIC |
Not every notice has a state. |
status |
In Liquidation |
Company status on the notice. |
from, to |
2026-09-01 |
Published date, YYYY-MM-DD. |
include_deregistration |
true |
Off by default, since the large majority of notices are deregistrations. On by default when you search by ACN. |
sort |
published_asc |
Default is newest first. |
limit, page |
50, 2 |
Max limit is 100. |
since |
1042 |
Cursor polling. See below. |
Examples:
/v1/notices?q=drifta/v1/notices?state=QLD&appointment_type=Court Liquidation&from=2026-09-01/v1/notices?acn=643233676Cursor polling with since
Section titled “Cursor polling with since”Pass since with the highest seq you’ve already seen, and the response switches to ascending order and returns only notices with a higher seq. Use meta.next_since from the response as the since value on your next call. since ignores sort and page.
next_since advances past notices that other filters excluded (for example the default include_deregistration=false), not just past notices actually returned, so a client polling with filters still makes progress instead of stalling on a filtered-out tail.
Sample response
Section titled “Sample response”curl "https://api.insolvencyalerts.com.au/v1/notices?q=briagin" \ -H "X-API-Key: YOUR_API_KEY"{ "data": [ { "id": "6ce624e8-038a-4c93-acd1-06ed9be1974d", "company_name": "BRIAGIN PTY LIMITED", "acn": "163753428", "other_names": null, "notice_title": "NOTICE OF APPLICATION FOR WINDING UP ORDER", "legal_reference": "Paragraph 465A(1)(c)", "notice_code": "465A(1)(c)", "appointment_type": "Winding Up Application", "notice_purpose": "Winding up application", "state": "NSW", "company_status": "Registered", "is_deregistration": false, "published_date": "2026-09-17", "appointment_date": "2026-08-13", "source_url": "https://publishednotices.asic.gov.au/browsesearch-notices/notice-details/BRIAGIN-PTY-LIMITED-163753428/6ce624e8-038a-4c93-acd1-06ed9be1974d", "seq": 4821 } ], "meta": { "page": 1, "limit": 20, "total": 1, "total_is_capped": false, "total_pages": 1 }, "source": { "name": "ASIC Published Notices", "url": "https://publishednotices.asic.gov.au", "note": "Data from the Australian Securities & Investments Commission. Check the source notice before relying on it." }}For broad queries, meta.total is capped at 1000 and meta.total_is_capped is true. Exact totals over hundreds of thousands of rows are slow, so use /v1/stats when you need a real count.
Other read endpoints
Section titled “Other read endpoints”GET /v1/notices/{id}: one notice.GET /v1/companies/{acn_or_abn}: every notice for one company, newest first, with register data attached. Accepts a 9-digit ACN or an 11-digit ABN. A company that’s in the register but has no notices yet returns HTTP 200 withnotice_count: 0, not a 404; a 404 means neither the register nor the notices table has anything for that identifier. The register is a weekly snapshot, not live data.GET /v1/filters: every filter value in the database, with counts. Useful for building dropdowns.GET /v1/stats?group_by=state&from=2026-01-01&to=2026-06-30: grouped counts.group_byacceptsappointment_type,notice_purpose,state,notice_codeormonth. Cached for an hour.GET /health: collector status. No key needed.