AusTender Contract Notices: Australian Government Contracts avatar

AusTender Contract Notices: Australian Government Contracts

Pricing

from $1.20 / 1,000 contract notices

Go to Apify Store
AusTender Contract Notices: Australian Government Contracts

AusTender Contract Notices: Australian Government Contracts

Australian Government contract notices (awards) from AusTender by CN id, date, agency or UNSPSC, with alerts. Awards only, not open tenders. Derived data, CC BY 3.0 AU. Not affiliated with the Department of Finance.

Pricing

from $1.20 / 1,000 contract notices

Rating

0.0

(0)

Developer

Russell Yapp

Russell Yapp

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Features

Limited permissions

Share

No open tenders: AusTender Contract Notices looks up, searches and monitors Australian Government contract awards (AusTender contract notices), read from the AusTender API.

cnIdagencyvaluecurrencycontractStartcontractEndpublishedAtprocurementMethod
CN4280221National Indigenous Australians Agency44490.6AUD2026-09-22T14:00:00Z2027-06-29T14:00:00Z2026-10-01T23:51:13ZLimited tender

A Console default run returns up to 3 notices: $0.006 on the Free plan. Through the API, maxItems defaults to 1,000 (up to $2.00 on Free), so set it.

Run it with the default input.

What you get

One row per AusTender contract notice or amendment: the CN id, the agency, the contract value and currency, the UNSPSC codes, the procurement method, the contract start and end dates, when it was published and last modified, the number of amendments, and a notice link (noticeUrl). Only contract notices (awards and their amendments) are covered, not open tenders. Supplier names and identifiers are left out (see "What is left out"). The dataset has one view, overview ("Contract notices"), a table of the main fields.

Mode (mode)What it does
lookupReturns the latest version of each CN id you name in cnIds (up to 20), with its amendment count.
searchThe default. Returns notices in a date range of up to 92 days (default 31), with filters.
alertA monitor named by alertId: returns only notices it has not sent before, from the last 14 days of last-modified dates.
expiringA watch named by watchId: returns contracts whose published end date falls in the next withinDays days and that it has not sent before.

Quick spec for AI agents

All fields are optional except cnIds (lookup), alertId (alert) and watchId (expiring). An unknown field refuses the run before anything is read or charged.

FieldTypeDefaultLimitMeaning
modetextsearchsearch, lookup, alert, expiringWhat to run.
cnIdslistnone20Lookup: CN ids such as CN4280221.
dateTypetextcontractPublishedcontractPublished, contractLastModified, contractStart, contractEndSearch: which date the range applies to.
dateFrom, dateToYYYY-MM-DD30 days before dateTo; todayrange at most 92 daysSearch: the date range, UTC, inclusive.
agencieslistnone20 entries, 200 characters eachPart of the agency name.
unspscCodeslistnone20 entries, 2 to 8 digitsUNSPSC code prefixes.
valueMin, valueMaxintegernone0 or moreContract value in AUD.
procurementMethodslistnoneOpen tender, Limited tender, Prequalified tenderAs published.
contractStartFrom, contractStartTo, contractEndFrom, contractEndToYYYY-MM-DDnonenot in expiring modeContract start and end filters.
alertId, watchIdtextnone1 to 40 of a-z, 0-9, hyphenNames the alert or watch.
firstRunLookbackDaysinteger11 to 14Alert: days returned on the first run.
withinDays, firstRuninteger, text90, all1 to 92; all or skipExpiring: window; skip records it without charge.
maxItemsinteger1000 (Console form: 3)1 to 100,000Most rows returned, and so the most you pay for.

Smallest inputs that run:

  • Search: {"maxItems": 3}
  • Lookup: {"mode": "lookup", "cnIds": ["CN4280221"]}
  • Alert: {"mode": "alert", "alertId": "example-alert", "maxItems": 50}
  • Expiring: {"mode": "expiring", "watchId": "example-watch", "firstRun": "skip"}

Output: one row per notice (fields as in the dataset schema). RUN_SUMMARY in the run's key-value store holds the counts: status, pushed, and by mode notFound (lookup) or matched, alreadySent, truncatedByMaxItems, agedOutLeaving and agedOutLeft (alert).

Source and licence

AusTender materials are released by the Department of Finance.

AusTender materials are subject to change and should be verified on the AusTender website to ensure the information is up to date and correct: www.tenders.gov.au.

Derived and modified by Yappman Data from AusTender contract notices: fields selected, renamed and redacted, and supplier names and identifiers left out. A days-to-expiry figure is calculated by Yappman Data from the published contract end date.

Licensed under CC BY 3.0 AU: https://creativecommons.org/licenses/by/3.0/au/

This Actor is independent: it is not affiliated with or endorsed by the Department of Finance or AusTender.

Only contracts at or above the reporting threshold are published on AusTender: A$10,000 for most agencies, higher for corporate Commonwealth entities (Commonwealth Procurement Rules, paragraph 7.18).

What is left out

No supplier names. Version 1 outputs no supplier's name, legal name, ABN or party id, and has no supplier filter. Each row's notice link (noticeUrl) opens the notice on the AusTender API, which does name the supplier. Contact details and addresses are never read.

No subject line. A notice's description (its subject line) can name a person, so it is never output and there is no keyword search. The title field is the agency's contract reference as published (a reference code), not a subject. It is output only when it is reference-shaped (it contains a digit, contains no whitespace and is at most 40 characters); otherwise it is null. A reference can still be looked up on AusTender, which leads to the notice and its supplier.

Modes

  • Lookup (cnIds): up to 20 CN ids, such as CN4280221 or an amendment id such as CN4271813-A1. Each returns the latest version of its notice, with its amendment count. An id AusTender does not know is reported as not found and costs nothing.
  • Search: a date range of up to 92 days (default 31) on one of four dates (dateType), with filters for the agency, UNSPSC code prefixes, value in AUD, procurement method, and contract start and end dates.
  • Monitor (mode alert, named by alertId): intended to be run each working day. For example, set agencies to Defence and unspscCodes to 81, and each run returns only the matching notices it has not returned before. Each run reads the last 14 days of contract last-modified dates, so amendments are caught, and returns only the notices this alert has never sent before. On its first run it returns the last firstRunLookbackDays days and records the rest as seen, without charge. A monitor keeps what it has sent in your own key-value store, named after the alert.
  • Expiring (mode expiring, named by watchId): the contracts whose published end date falls in the next withinDays days (1 to 92, default 90) and that this watch has not returned before. See Expiring contracts below.

Set an alert's filters and maxItems for its volume. An alert sends at most maxItems new notices a run, newest first. Narrow it with the filters first: agencies, unspscCodes, valueMin and valueMax, procurementMethods, and the contract start and end dates. Then set maxItems to cover the alert's expected filtered daily volume; otherwise its backlog grows and older notices can age out of the 14-day window unsent. The run summary counts those that will leave the window at 00:00 UTC unless a run sends them first (agedOutLeaving) and those that have left it unsent (agedOutLeft); none of them is ever charged. For scale: about 930 contract notices were modified on AusTender between 28 Oct 17:24 UTC and 29 Oct 07:12 UTC (an owner canary of 29 Oct 2026); unfiltered daily volume is in the high hundreds.

Do not put a person's name in alertId. It is kept in the alert's store name, its ledger, the run summary and the status message, in your account.

The run's RUN_SUMMARY record holds counts only, never what you typed (apart from the alert's or watch's name, and withinDays).

Expiring contracts

Data: AusTender, Department of Finance, CC BY 3.0 AU; see Source and licence above.

Expiring mode (mode expiring) returns the contracts whose published end date is from today to today plus withinDays (both days included, UTC days) and that this watch has not returned before. Each notice id is returned once. An amendment (an id such as CN4271813-A1) is a new notice: it is returned and charged as its own row when its end date is inside the window, and an earlier version of the same notice that the same read also holds is left out. An original already superseded by an amendment that falls outside the window may still be returned. Each row has daysToExpiry, the whole days from the run's date to the contract end date (0 on the day it ends), calculated by Yappman Data from the published end date; it is null in every other mode.

  • Input: watchId (required: 1 to 40 characters of a-z, 0-9 and a hyphen), withinDays (1 to 92, default 90), firstRun, the filters agencies, unspscCodes, valueMin and valueMax, procurementMethods, and maxItems. dateType, dateFrom, dateTo and the contract start and end filters are not offered in this mode, and are refused.
  • First run: firstRun all (the default) returns what is already in the window, soonest end date first, up to maxItems; the rest follow on later runs while they are still in the window. skip records the window as seen without charge, so later runs return only contracts that enter it.
  • State: the watch keeps what it has returned in your own key-value store au-cn-expiring-, then the watchId, separate from any alert's, for 100 days. Do not put a person's name in watchId: it is kept in that store name, the ledger, the run summary and the status message, in your account.
  • Cost: each row returned is one notice event, as in the other modes; there is no run fee. A first run with firstRun all can be large: set the filters and maxItems first. A large window is returned over several runs, and each run charges for up to maxItems new notices: for example, a 7-day window holding 456 notices at maxItems 5 takes about 92 runs and about $0.91 at Free-plan prices. skip is the cheap way to avoid the backlog. If a watch's stored record is lost or reset (for example its key-value store is deleted), the next run with firstRun all returns the whole window again and charges for it: use skip after a reset. A watch's record keeps 100 days of what it has returned, up to a cap of 1 MB: a hot watch that returns roughly 22,000 notices within 100 days reaches it, by design. It then stops before it sends or charges anything (status ledgerFull) and recovers as its oldest days pass 100 days; to carry on sooner, narrow the filters, or start a new watchId (its first run then returns the window again, so use skip if you do not want that).

A contract ending does not mean a tender is coming. The end date is the figure on the notice version returned, not a forecast, and a later amendment can change it: check noticeUrl. Nothing here is advice. This Actor is independent of the Department of Finance and AusTender. Expiring mode was first checked on Apify with test runs on a candidate build on 3 Nov 2026.

Pricing

Pay per event: you pay only for the notices a run returns.

EventChargedPrice on the Free planBronzeSilverGold and above
noticeEach row returned (lookup, search and alert)$0.002 ($2.00 per 1,000)$0.0018$0.0016$0.0012

There is no start or run fee: a run that returns no notices costs nothing. Worked costs at Free-plan prices: one notice looked up, $0.002; a Console default run (the form starts maxItems at 3, so up to 3 notices), $0.006; an API run with no maxItems (default 1,000), or a 31-day search capped at 1,000 rows, up to $2.00. For alerts: a filtered alert (for example one agency with valueMin 100000, about 5 to 20 notices a day) with maxItems 50 costs about $0.01 to $0.04 a day; an unfiltered alert with maxItems 1000 costs up to $2.00 a day, about $60 a month on the Free plan and $36 on Gold and above.

Removal and objection

If a notice names you, or your business as a sole trader, you can ask for it to be left out of this Actor's output: email info@yappman.com with the CN id. A notice left out by its CN id is left out whole, with all of its amendments, later ones included. To object to all of your notices, including future ones, give your ABN; the Actor holds it only as a keyed hash, matched before anything is output: when any version of a notice that a run reads names that ABN, the whole notice, with its amendments, is left out of that run. We act on a request within one month. A notice left out on request is treated as if it were not found: it is never returned or charged.

Status

Built and checked on Apify (S5, 28 and 29 Oct 2026): lookup, search and alert, with charging and the removal lists. Expiring mode was first checked on Apify on 3 Nov 2026.

Reviews

Ratings and reviews on the Store page help other buyers judge whether this Actor fits their use, whatever your experience.