AusTender Contract Alerts: New Australian Gov Contracts

Get new Australian government contract notices by keyword, UNSPSC code, agency or supplier, as soon as AusTender publishes them. Every row is one awarded contract: the buying agency, the supplier and its ABN, the value in AUD, the start and end dates and the procurement method, read from the Department of Finance's own open-data feed. Turn on monitoring mode and run it on a schedule to get only the notices that are new since your last run, charged per notice and free on a quiet day.

Who uses it: suppliers tracking what competitors win, business-development teams building a pipeline from contracts that are about to expire, journalists and researchers following government spending. It lists contracts that have been awarded, not tenders still open for bids.

Related actors: for UK notices use UK Find a Tender Alerts, for EU notices EU Tender Alerts. This actor is Australia only.

How to use

1. In the Apify Console. Open the actor page and click Start — the keywords field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~australia-austender-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"keywords":["services"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "keywords": [
    "services"
  ]
}

One keyword or phrase per line, matched against the contract description, the supplier name and the agency reference. Combine with UNSPSC codes and agency names below (optional). Leave empty to list recent notices without a keyword filter. Accepted formats: consulting, IT services, "security guard".

One combined search runs per call. Keywords are matched against the contract description, the supplier name and the agency reference; UNSPSC codes are prefix-matched (81 = engineering and IT services), agency names are contains-matched. Filters run after the fetch, and the date window always applies, so an empty keyword list still returns the newest notices. The search run itself is free; you are billed per notice actually returned. The feed publishes with about a day of lag.

Output

One row per contract notice, for example:

query	found	status	searchSummary	noticeCount	truncated	monitorStatus	notices	noticeId	ocid	agencyReference	description	buyerName	buyerAbn	supplierName	supplierAbn	supplierCountry	supplierState	unspscCode	valueAud	currency	signedAt	publishedAt	startDate	endDate	procurementMethod	procurementMethodDetails	exemptionReason	contractStatus	noticeUrl	isNew	firstSeenAt	scrapedAt
services	true	OK					<all notices (full list)>	<contract notice (cn) number>											<contract value (aud)>							<procurement method (detail)>				<is this notice new?>		1970-01-01T00:00:00.000Z

A miss comes back as a row with "found": false and is never charged. valueAud is null when the notice publishes no value — never 0. Contact people, emails and phone numbers are not returned.

Pricing

• Contract notice returned: $3 per 1,000 notices

Plus a $0.002 start fee per run. Each event above is billed independently, only when it actually returns data — misses (found:false) are never charged.

Example runs

Paste any of these into the Input tab and press Start. All three return rows with no key, no token and no account of your own beyond an Apify login.

The newest 20 notices, no filter. The default shape.

{
  "sinceDays": 3,
  "maxResults": 20
}

Consulting contracts over A$100,000 in the last 14 days.

{
  "keywords": ["consulting"],
  "minValueAud": 100000,
  "sinceDays": 14
}

Contracts awarded without open competition (limited tender) to the Department of Defence, with monitoring on.

{
  "buyerNames": ["Defence"],
  "procurementMethod": "limited",
  "sinceDays": 7,
  "onlyNewSinceLastRun": true
}

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~australia-austender-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"keywords":["services"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~australia-austender-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"keywords":["services"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~australia-austender-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"keywords":["{{search}}"]}, mapping the row's search into the keywords array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "austender API" — the agent will find and run this actor.