AusTender Contract Awards Scraper avatar

AusTender Contract Awards Scraper

Pricing

Pay per event

Go to Apify Store
AusTender Contract Awards Scraper

AusTender Contract Awards Scraper

Extract Australian Government contract awards with buyers, suppliers, ABNs, values, dates, contacts, and UNSPSC codes. Export clean data or schedule recurring monitoringβ€”no AusTender API key required.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

Extract Australian Government contract awards from the official AusTender OCDS API. Get buyer and supplier names, ABNs, award values, contract periods, contacts, UNSPSC codes, and source identifiers in clean JSON, CSV, Excel, or XML.

The AusTender Contract Awards Scraper supports exact Contract Notice lookups and repeatable date-range monitoring. It requires no AusTender login, browser, proxy, or external API key.

What does AusTender Contract Awards Scraper do?

This Actor turns nested AusTender Open Contracting Data Standard releases into one flat row per federal contract award. Use it to:

  • 🎯 look up one or many known Contract Notice IDs such as CN4256428;
  • πŸ“… find awards by publication or last-modified date;
  • ⏳ find contracts by start or end date for pipeline and recompete research;
  • 🏒 connect Australian Government buyers with awarded suppliers and ABNs;
  • πŸ’° analyze contract values, currencies, periods, and UNSPSC categories;
  • πŸ”„ schedule a daily extraction without maintaining API pagination code.

The Actor calls the official anonymous JSON API directly and automatically splits date windows when the source reaches its response cap.

Who is this AusTender scraper for?

Government suppliers and business development teams

  • Monitor competitor wins by supplier and agency.
  • Find expiring incumbent contracts before a likely recompete.
  • Enrich CRM accounts with Contract Notice IDs, ABNs, values, and dates.

Procurement and category analysts

  • Build agency-spend and supplier-concentration dashboards.
  • Group awards by UNSPSC category or procurement method.
  • Refresh a warehouse from publication or modification windows.

Journalists and researchers

  • Trace public spending to named suppliers.
  • Preserve release IDs and official source URLs for reproducible analysis.
  • Compare contract periods, values, and purchasing entities over time.

Consultants and data teams

  • Feed Australian procurement intelligence into Sheets, BigQuery, Snowflake, or a client portal.
  • Trigger alerts when a chosen date window produces new awards.
  • Use exact lookups as a dependable enrichment step in automated workflows.

Why use this Australian Government contracts scraper?

  • βœ… Official source β€” data comes from the Australian Department of Finance AusTender OCDS API.
  • βœ… No credentials β€” no AusTender account or third-party API subscription is needed.
  • βœ… Award-focused β€” output centers on signed and awarded contracts, not only open opportunities.
  • βœ… Normalized rows β€” nested OCDS parties, awards, and contracts become export-friendly columns.
  • βœ… Cap-aware extraction β€” full 100-release windows are automatically subdivided.
  • βœ… Low overhead β€” direct HTTP extraction runs with 256 MB memory and no browser.
  • βœ… Repeatable automation β€” run from the Console, API, scheduler, webhook, Make, Zapier, or MCP.

What AusTender contract data can you extract?

CategoryFields
Source identityocid, releaseId, releaseDate, releaseTags, contractNoticeId, sourceUrl
AwardawardId, awardStatus, awardDate
ContractcontractStatus, dateSigned, title, description
BuyerbuyerName, buyerAbn, buyerContactName, buyerContactEmail
SuppliersupplierName, supplierAbn, locality, region, postcode, country, contact name, email
ClassificationunspscCode, procurementMethod, procurementMethodDetails
Commercial termscontractStartDate, contractEndDate, amount, currency
ExtractionscrapedAt

Fields absent from an upstream OCDS release are omitted rather than replaced with invented values. Amounts are returned as numbers so they can be summed immediately.

How much does it cost to scrape AusTender contract awards?

This Actor uses pay-per-event pricing. A small start fee covers initialization, followed by a charge for each contract award saved. All Apify platform costs are included.

EventFreeStarterScaleBusiness
Run started$0.005$0.005$0.005$0.005
Contract award$0.0005276$0.00045878$0.00035785$0.00027527

Higher plans receive additional volume discounts. For example, 100 contract awards cost about $0.058 on the Free plan or $0.051 on Starter, including the start fee. The Apify Free plan's included credits are enough for many small lookups and monitoring tests.

Prices are formula-derived from a representative 256 MB cloud run and include the fixed start charge.

How to scrape AusTender contract awards

  1. Open AusTender Contract Awards Scraper.
  2. Add one or more Contract Notice IDs, or enter both ends of a date range.
  3. Choose the date field: publication, last modification, contract start, or contract end.
  4. Set a practical maximum number of contract awards.
  5. Click Start.
  6. Review the Contract awards dataset view.
  7. Export the results as JSON, CSV, Excel, XML, or connect them to another app.

Start with the prefilled exact lookup for a fast, inexpensive first run.

Input parameters

ParameterTypeDefaultPurpose
noticeIdsstring array[]Exact AusTender IDs such as CN4256428
dateTypestringcontractPublishedDate dimension used by the range search
fromDateISO date stringnoneInclusive beginning of the date range
toDateISO date stringnoneEnd of the date range
maxItemsinteger100Maximum normalized contract rows to save
windowHoursinteger24Initial API date-window size before automatic splitting

Provide at least one Contract Notice ID or both fromDate and toDate. Date ranges may span up to 366 days per run.

Input examples

Look up exact Contract Notices

{
"noticeIds": ["CN4256428", "CN4256861"],
"maxItems": 10
}

Monitor newly published awards

{
"dateType": "contractPublished",
"fromDate": "2026-07-01T00:00:00Z",
"toDate": "2026-07-02T00:00:00Z",
"maxItems": 1000,
"windowHours": 2
}

Find contracts approaching their end date

{
"dateType": "contractEnd",
"fromDate": "2027-01-01T00:00:00Z",
"toDate": "2027-01-08T00:00:00Z",
"maxItems": 2000,
"windowHours": 24
}

Output example

{
"ocid": "prod-6527ed2fd89c42f28d153544d3492b1d",
"releaseId": "prod-6527ed2fd89c42f28d153544d3492b1d-be5e877d0a98326594417ad1dca7bf93",
"releaseDate": "2026-07-01T00:54:05Z",
"releaseTags": ["contract"],
"contractNoticeId": "CN4256428",
"awardStatus": "active",
"contractStatus": "active",
"title": "C00359",
"description": "IMT VSA6 items MS",
"buyerName": "Australian Institute of Family Studies",
"buyerAbn": "64001053079",
"supplierName": "Data#3 Limited",
"supplierAbn": "31010545267",
"supplierLocality": "Brisbane",
"supplierRegion": "QLD",
"unspscCode": "43200000",
"procurementMethod": "open",
"contractStartDate": "2026-06-30T14:00:00Z",
"contractEndDate": "2031-06-29T14:00:00Z",
"amount": 743033.67,
"currency": "AUD",
"sourceUrl": "https://api.tenders.gov.au/ocds/findById/CN4256428"
}

Date search modes

Use contractPublished for daily new-award ingestion. Use contractLastModified to refresh records that AusTender changed after publication. Use contractStart to analyze contracts beginning in a future delivery period. Use contractEnd to identify expiring contracts and potential recompete windows.

Date timestamps must use ISO-8601, ideally UTC with a trailing Z. The Actor preserves the official release date separately from contract start, end, award, and signature dates.

Exact Contract Notice lookups

Exact lookup is the fastest route when you already have CN identifiers. The Actor validates IDs before requesting the source and fails closed on malformed values. Duplicate IDs are removed from the input. When IDs and a date range are combined, exact lookups run first and duplicates are suppressed across both routes.

Handling AusTender API response limits

The official API can return 100 releases for a date query. A full response may indicate that more records exist inside the requested interval. The Actor therefore bisects capped windows repeatedly, down to one minute.

If 100 releases still occupy a one-minute window, the run logs a warning because the public endpoint exposes no cursor for that unusually dense interval. Choose a lower windowHours setting for easier log inspection; automatic splitting works regardless of the initial value.

Tips for best results

  • πŸš€ Start with one known Contract Notice ID to validate your workflow.
  • πŸ• Schedule publication-date jobs shortly after the period you want to ingest.
  • πŸ” Use last-modified searches to keep a warehouse synchronized.
  • πŸ“‰ Keep maxItems low during workflow development.
  • 🧩 Join records on contractNoticeId, and retain releaseId to distinguish revisions.
  • 🏷️ Group by unspscCode for category intelligence.
  • πŸ“† Search contract end dates months ahead for recompete planning.
  • πŸ”’ Treat contact details responsibly and comply with applicable privacy and outreach rules.

Integrations and procurement workflows

AusTender β†’ Google Sheets

Schedule a daily run and append contract awards to a shared supplier-intelligence sheet. Use buyer, supplier, amount, and end date columns for team review.

AusTender β†’ Slack or Microsoft Teams

Trigger a webhook when a run completes, filter new rows by agency or UNSPSC, and alert the relevant account owner.

AusTender β†’ BigQuery or Snowflake

Load normalized rows into an analytics warehouse. Use releaseId for idempotency and contractNoticeId for contract-level reporting.

AusTender β†’ Make or Zapier

Create CRM opportunities for high-value or soon-expiring contracts and attach the official source URL.

AusTender β†’ scheduled recompete monitor

Run contractEnd searches weekly, compare against prior results, and notify business development teams about incumbent contracts entering a target horizon.

Using the AusTender scraper API with Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/austender-contract-awards-scraper').call({
noticeIds: ['CN4256428'],
maxItems: 10,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Using the AusTender scraper API with Python

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/austender-contract-awards-scraper').call(run_input={
'noticeIds': ['CN4256428'],
'maxItems': 10,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

Using the AusTender scraper API with cURL

curl -X POST \
'https://api.apify.com/v2/acts/automation-lab~austender-contract-awards-scraper/runs?token=YOUR_APIFY_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"noticeIds":["CN4256428"],"maxItems":10}'

Poll the returned run ID, then download items from its defaultDatasetId. Do not place long-lived tokens in shared scripts or source control.

Use with AI agents via MCP

AusTender Contract Awards Scraper can be used by AI assistants through the Model Context Protocol.

For Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/austender-contract-awards-scraper"

For Claude Desktop, Cursor, or VS Code, add:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=automation-lab/austender-contract-awards-scraper"
}
}
}

Example prompts:

  • β€œUse automation-lab/austender-contract-awards-scraper to look up CN4256428 and summarize the buyer, supplier, value, and contract period.”
  • β€œFind Australian Government contracts ending next quarter and group them by supplier ABN.”
  • β€œExtract yesterday's newly published AusTender awards and identify the five largest values.”

Authentication uses your Apify account on first connection.

Scheduling a daily AusTender monitor

Create an Apify schedule with a publication window matching the period since the prior run. Store the last successful timestamp in your downstream system, or use fixed non-overlapping UTC windows. Deduplicate downstream on contractNoticeId plus releaseId.

For updates to previously published records, add a separate contractLastModified schedule. A webhook can start data loading or alerting as soon as each run finishes.

Data quality and missing fields

AusTender publishes OCDS records with optional nested fields. Some contracts may omit a contact name, address component, title, classification, or procurement-method detail. The Actor does not guess missing data.

Supplier references are matched to release parties by ID, with the OCDS supplier role as a fallback. Awards are matched to contracts through awardID where available. Always retain source identifiers when merging this dataset with another system.

AusTender contract data is public government procurement information exposed through an official anonymous API. The API package identifies the Department of Finance as publisher and uses an open-data license.

You are responsible for your use of the results. Follow the source terms, avoid excessive request rates, respect privacy obligations, and do not use contact information for unlawful or misleading outreach. This Actor uses conservative direct requests and bounded retries.

FAQ

How fast is the AusTender Contract Awards Scraper?

Exact lookups commonly finish in seconds. Date runs depend on interval density because full source responses are split to avoid missing records.

Does it need an AusTender API key or login?

No. The official OCDS endpoints used by this Actor are publicly accessible without credentials.

What is the difference between this Actor and the AusTender website?

The website is designed for interactive procurement browsing. This Actor provides normalized rows, output limits, scheduled runs, API access, exports, retries, cap handling, and integrations.

Why did my date search return no results?

Confirm that both dates are valid ISO-8601 values, the start precedes the end, and the selected date dimension matches your intent. A contract may have a publication date but no start or end date inside the same period.

Why are some supplier or contact fields missing?

Those fields are optional in upstream OCDS releases. The Actor omits unavailable values rather than fabricating them.

Can I search more than one year?

Each run accepts at most 366 days to keep request volume controlled. Create several adjacent runs or schedules for longer historical backfills.

Can I monitor contract changes?

Yes. Use contractLastModified with recurring non-overlapping date windows and retain the release ID for revision-aware processing.

Will I receive duplicate contracts?

The Actor deduplicates the same Contract Notice and release within a run. A later modified release can correctly have a different release ID; handle that as an update downstream.

Other government procurement scrapers

Use these actors together to build a multi-country public procurement feed while preserving each source's native identifiers.

Support

If a run fails, include the run URL, input route, date type, and redacted input in an Apify issue. For empty results, first test one known Contract Notice ID and inspect the selected date dimension. Source-side outages and throttling are retried conservatively; persistent API errors remain visible as failed runs instead of silent empty datasets.