Australia Government Data Search

Search Australia-focused public data across business, construction, health, legal/IP, and procurement products in one run.

• ✅ Search 28 Australia-focused SIP data products with one keyword list
• ✅ Cover ASIC company data, planning permits, health and NDIS datasets, IP Australia records, insolvency, legislation, and procurement
• ✅ Use it without coding, or connect it to ChatGPT, Claude, MCP, Make, Zapier, or n8n
• ✅ Turn categories on only when you need them
• ✅ Free $5 Apify credit is enough to test real searches before you pay anything

Australian public data is spread across federal, state, territory, and agency-specific systems. Company and licensing checks live in ASIC. IP records sit with IP Australia. Planning data is distributed across local or state-level sources. Health and compliance data sits across AIHW, MBS, NDIS, and related datasets. This Actor gives you one search layer across those Australia-focused SIP products, then returns structured results in one dataset you can review, export, or feed into downstream workflows.

This Actor is best for discovery, topic scanning, monitoring, and early-stage research. It is not a substitute for deep source-by-source compliance analysis, and it does not turn all Australian public data into one perfectly standardized national master database.

---

What you can do with it

1. Search Australian company and ASIC signals in one run

If you are doing entity research in Australia, start with the business category.

What you enter

• Search terms like BHP, Commonwealth Bank, Woolworths, credit licence, liquidator
• Keep ASIC business & company data enabled

What you get back

• ASIC company matches
• ASIC business-name matches
• Credit-licensee matches
• Registered-auditor and SMSF-auditor matches
• Liquidator matches
• Banned or disqualified person and organisation matches

This is useful when you want a faster answer to questions like:

• Is this entity registered?
• Does it show up in relevant ASIC lists?
• Are there risk or compliance signals I should inspect further?

2. Search Australian planning and development data

If your topic is construction, land use, or active development applications, the construction category gives you a practical first-pass entry point.

What you enter

• Search terms like Brisbane, Casey, development application, subdivision, planning
• Keep construction & planning data enabled

What you get back

• ACT active development application matches
• Moreton Bay development application matches
• Casey planning permit matches

This works well when you want a quick scan of planning activity across the currently configured Australia planning products without checking each source one by one.

3. Search Australian health, Medicare, and NDIS-related datasets

The health category is useful when you want public-data signals across health system metrics, hospital data, Medicare statistics, and compliance datasets.

What you enter

• Search terms like diabetes, oncology, hospital, MBS, NDIS
• Keep health & NDIS data enabled

What you get back

• AIHW hospital-statistics matches
• Cancer incidence and mortality data matches
• MBS group statistics and patient-demographics matches
• NDIS compliance-action matches
• Health aggregate results

This is useful for healthcare research, system-level analysis, and public-data discovery.

4. Search Australian legal, insolvency, and IP sources

Legal is off by default, but it can be enabled when you want legislation, insolvency, and IP records in the same run.

What you enter

• Search terms like patent, trademark, design, insolvency, legislation
• Enable legal & IP data

What you get back

• IP Australia patent, trademark, and design search matches
• IP registry matches
• AFSA personal-insolvency matches
• Federal legislation matches
• Legal aggregate results

This is useful when you want to connect IP, insolvency, and legislation signals in one search pass.

5. Search Australian procurement records

Procurement is off by default, but you can enable it when you want public contracting signals from the configured AusTender products.

What you enter

• Search terms like cybersecurity, defence, Deloitte, consulting
• Enable AusTender procurement

What you get back

• AusTender historical-contract matches
• AusTender OCDS contract matches

This is useful for public-sector market research, supplier tracking, and contract discovery.

6. Connect Australia public-data discovery to AI or automation

This Actor works for manual use, but it is also designed to plug into broader workflows.

What you enter

• Search terms and category toggles in Apify
• Or the same parameters through API, MCP, or automation tools

What you get back

• Structured records in the dataset
• Stable SIP metadata fields such as _product_id, _source, _search_term, and _collected_at
• Output that is easy to export, summarize, monitor, or pass into spreadsheets and AI agents

This is the right pattern when you want search once, reuse everywhere.

---

How to use

You do not need to write code to use this Actor.

1. Open the Actor and click Try for free
2. Enter one or more search terms such as BHP, patent, hospital, or cybersecurity
3. Choose which categories to include:
   • ASIC business & company data
   • construction & planning data
   • health & NDIS data
   • legal & IP data
   • AusTender procurement
4. Set max results per source
5. Run the Actor
6. Review the results in Apify or export them as JSON, CSV, Excel, XML, or RSS

By default, business, construction, and health are enabled. Legal and procurement are available when you want a broader scan.

---

What you get back

The Actor returns structured records from the selected Australia-focused products. Exact fields vary by source, because an ASIC company record, a planning permit row, an MBS statistical record, a patent filing, and an AusTender contract are not the same kind of object.

Common SIP metadata fields include:

Field	What it means
_product_id	The SIP product that returned the record
_source	Human-readable source label
_search_term	The keyword that produced the record
_collected_at	UTC collection timestamp

In the Output tab, the default overview highlights fields such as:

• name
• type
• status
• state
• _source
• _search_term
• _collected_at

Depending on the enabled category, you may also see fields like:

• company_name
• acn
• abn
• license_number
• address
• state
• application_type
• indicator
• filing_number
• contract_value
• supplier
• source_url

Here is a simplified example:

[
  {
    "company_name": "BHP GROUP LIMITED",
    "acn": "004028077",
    "status": "Registered",
    "_product_id": "au_asic_companies",
    "_source": "asic_companies",
    "_search_term": "BHP"
  },
  {
    "supplier": "Accenture Australia",
    "contract_value": "2400000",
    "status": "awarded",
    "_product_id": "au_austender_ocds_contracts",
    "_source": "austender_ocds_contracts",
    "_search_term": "cybersecurity"
  }
]

The goal is not to force every Australian source into identical semantics. The goal is to make cross-source discovery fast enough to act on.

---

Coverage

This Actor currently searches 28 Australia-focused SIP data products across 5 categories:

Category	What is included	Count
Business	ASIC companies, names, licences, auditors, liquidators, banned/disqualified entities	8
Construction	ACT, Moreton Bay, and Casey planning/development sources	3
Health	AIHW, cancer data, MBS, NDIS, and health aggregate	6
Legal	IP Australia search/registry products, AFSA insolvency, federal legislation, legal aggregate	9
Procurement	AusTender historical contracts and OCDS contracts	2

There are two important boundaries to state clearly.

First:

• These are 28 SIP data products, not 28 completely separate Australian institutions
• Some products are direct record-style sources
• Some categories include aggregate products, such as au_health and au_legal_aggregate

Second:

• Some products return entity or operational records like ASIC company matches, planning permits, or AusTender contracts
• Some return statistical or analytical rows like MBS or cancer datasets
• Some return IP or legal discovery data such as patent, trademark, design, insolvency, or legislation records

So the right mental model is: this Actor is an Australia public-data discovery layer across multiple source types, not a single fully standardized Australian government master database.

---

Pricing

This Actor is currently listed on Apify with pay per usage pricing.

That means your cost depends on:

• your Apify plan
• how often you run the Actor
• how many results you return
• how many categories and sources you enable

For the current pricing page, see:

• https://apify.com/lentic_clockss/australia-data-search/pricing

In practice, the free Apify credit is enough to test real searches, inspect the output shape, and decide whether this workflow fits your research or automation use case before you pay anything.

---

Connect to your tools

You can use this Actor manually or connect it to your stack.

Tool	How to use it
Apify Console	Run it directly with a form input
Make.com	Use the Actor via Apify integration
Zapier / n8n	Trigger runs and send results into downstream workflows
ChatGPT / Claude	Connect through Apify MCP
Scripts / apps	Call it through the Apify API

If you want to use it with AI workflows, Apify MCP is usually the cleanest path.

---

When to use something else

This Actor is a strong fit when you want a broad Australia public-data entry point across companies, planning, health, legal/IP, and procurement topics.

Choose something else if you already know you need a narrower or deeper workflow:

• Use an ASIC-specific workflow if you need deep corporate-compliance or entity-resolution work
• Use a planning-specific workflow if you need permit-level or council-specific operational tracking
• Use a health-specific workflow if you need deep system analysis rather than mixed public-data discovery
• Use a procurement-specific workflow if you need tender operations or dedicated contract monitoring

In short, this Actor is best for finding relevant Australia public data quickly, not for replacing every source-specific operational workflow.

---

FAQ

Q: Does this search all Australian government data?
A: No. It searches 28 Australia-focused SIP data products across 5 categories. That is broad coverage, but not the whole Australian public-data universe.

Q: Are all 28 sources fully independent government institutions?
A: No. The 28 count includes aggregate products as well as narrower record-style products.

Q: Does it include both company and procurement searches?
A: Yes. You can search across ASIC and AusTender in the same actor if you enable both categories.

Q: Can I use it for IP lookups?
A: Yes. The legal & IP category includes patents, trademarks, and designs, plus insolvency and legislation.

Q: Can I export the results?
A: Yes. Apify datasets can be exported in formats like JSON, CSV, Excel, XML, and RSS.

Q: Is this only for developers?
A: No. It can be run directly in Apify with form inputs, and the developer-oriented examples are tucked into collapsible sections.

---

Related Actors

If you are building a broader APAC or public-data workflow, these may also fit:

Need	Actor
India public-sector data	India Government Data Search
Singapore public-sector data	Singapore Government Data Search
Switzerland public-sector data	Switzerland Government Data Search
Global company registries	Global Company Search

More actors: apify.com/lentic_clockss

---

Also Available

• Direct API: https://opendata.best/api/v1/data
• Postman collection: Fork and test
• GitHub: Collection source files