# Australian Government Contracts Ending Soon (AusTender) (`ausgovdata/au-contracts-ending`) Actor

Australian Government contracts from the official AusTender feed, ending in the next 1-730 days. Filter by keyword, value, state, category and buyer.

- **URL**: https://apify.com/ausgovdata/au-contracts-ending.md
- **Developed by:** [AusGovData](https://apify.com/ausgovdata) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Australian Government Contracts Ending Soon (AusTender)

Australian Government contracts that end in the next 1 to 730 days, so you can see the work
likely to come back to market: expiring contracts and early tender leads, listed before any
new tender is advertised.

### What you get

- One row per contract, from the official AusTender contract notices feed.
- What the contract is for: its title, description and UNSPSC category code.
- Who it is with: the government buyer and the supplier that won it, with ABNs.
- The published value in Australian dollars.
- Start date, end date and the whole days left until the contract ends.
- The supplier's state, postcode and suburb.
- Fields a notice does not publish are simply missing from that row, not blank.

### Who uses it

- **Bid writers and tender consultants** — a lead list of contracts coming up for renewal,
  sorted by how soon they end.
- **Business development teams that sell to government** — see where an incumbent's term is
  finishing and a procurement is likely.
- **Contract managers** — track when existing agreements expire.
- **Procurement researchers and analysts** — see who buys what, from whom, and for how much.

### How to use it

1. Set the inputs: how far ahead to look, keywords, a minimum value, supplier states, UNSPSC
   category prefixes or a buyer name.
2. Run it once, or save it as a task and schedule a daily or weekly run, so new end dates
   arrive without you doing anything.
3. Take the results from the dataset tab as CSV, Excel or JSON, or read them through the
   Apify API into Google Sheets, Airtable, Zapier, Make or your own tools.

### Input fields

| Field | Default | What it does |
|---|---|---|
| `daysAhead` | 90 | End dates between today and today plus this many days (1–730). |
| `keywords` | none | Title or description contains one of these words, case-insensitive. Leave empty for every contract. |
| `minValueAud` | 0 | Published value at or above this many Australian dollars. Contracts with no published value are left out when this is set. 0 means no minimum. |
| `states` | none | Supplier is in one of these states or territories (ACT, NSW, NT, QLD, SA, TAS, VIC, WA). Leave empty for all of them. |
| `unspscPrefixes` | none | Category code starts with one of these UNSPSC prefixes, e.g. "43" for information technology. Leave empty for all categories. |
| `buyerContains` | none | Buyer name contains this text, case-insensitive, e.g. "Department of Defence". Leave empty for all buyers. |
| `maxResults` | 1000 | Stop after this many contracts (1–10000). Each one is charged as one result. |
| `failIfEmpty` | off | For monitoring: mark the run as failed when nothing is found. Leave off for normal use. |

### Output example

One row from a local run on 2026-09-26 (`daysAhead` set to 7):

```json
{
  "id": "CN4279064",
  "title": "Graphic design and illustrative services",
  "description": "Graphic design and illustrative services",
  "buyerName": "Attorney-General's Department",
  "buyerAbn": "92661124436",
  "supplierName": "Think in Colour Pty Ltd",
  "supplierAbn": "32637562282",
  "valueAud": 35530,
  "published": "2026-09-25T01:57:08Z",
  "startDate": "2026-09-06T14:00:00Z",
  "endDate": "2026-09-29T14:00:00Z",
  "daysUntilEnd": 3,
  "state": "VIC",
  "postcode": "3071",
  "locality": "Thornbury",
  "categories": "82140000",
  "source": "austender",
  "licence": "Contains AusTender data, Department of Finance, licensed under CC BY 3.0 AU"
}
```

Fields a contract does not publish are simply missing. Results download as CSV, Excel or
JSON from the dataset tab.

### Pricing

You pay per result: one contract is one result, charged when its row is written. Rows you
never receive are not charged for, and the run stops by itself if it reaches the maximum
cost per run set on the run.

### FAQ

**How fresh is the data?**
Every run fetches the official AusTender feed live, so a run shows the contracts the feed
holds at that moment. AusTender publishes on business days, so a run on a weekend or public
holiday shows the same notices as the working day before. Schedule a daily run for a steady
flow.

**How much does a run cost?**
You pay only for the rows you receive: one contract, one charge. Set a maximum cost per run
and the run stops by itself when it is reached; rows that are never returned are never
charged for.

**Can I narrow it to the contracts I care about?**
Yes. Combine keywords, a minimum value, supplier states, UNSPSC category prefixes and a
buyer name in the same run — for example, information technology contracts (prefix "43")
worth at least $100,000 with a Defence buyer.

**Is this official data?**
Yes. It is the public AusTender OCDS API published by the Department of Finance, used under
CC BY 3.0 AU, and every row carries the attribution line.

**Does a contract ending mean a tender is coming?**
Sometimes. An ending contract is a likely re-tender, but the agency can extend it or buy the
same thing elsewhere. Treat the list as early tender leads, not a forecast.

**Can I get these contracts by email instead?**
Yes — [Tender Alerts](https://tenderalerts.au) emails the same official AusTender data,
daily or weekly, so you do not need to run anything.

### Data source and licence

The public AusTender OCDS API, Department of Finance,
`https://api.tenders.gov.au/ocds/findByDates/contractEnd/{from}/{to}`. Licence text,
copied from the source and kept on every row:

> Contains AusTender data, Department of Finance, licensed under CC BY 3.0 AU

CC BY 3.0 AU requires you to credit the Department of Finance.

### Privacy

Some AusTender suppliers are sole traders. When a supplier name looks like a person's name
(for example "SMITH, Jane" or "Jane Smith"), the row shows "Individual (sole trader)"
instead and drops that person's ABN, suburb and postcode, keeping only the state. Company
names (anything with a company word such as Pty Ltd) are kept as published.

### Limitations

A contract ending is a likely re-tender, not a promise that one is coming. Notices with no
published value, supplier address or category have those fields missing. End dates come
from the notice and are sometimes approximate. `daysUntilEnd` counts whole UTC days from
the run date, so a contract ending today is 0. When the list is longer than `maxResults`,
the run stops at the limit and the rest are neither returned nor charged for.

# Actor input Schema

## `daysAhead` (type: `integer`):

Look for contracts whose end date falls between today and today plus this many days.

## `keywords` (type: `array`):

Only contracts whose title or description contains at least one of these words (case-insensitive). Leave empty for every contract.

## `minValueAud` (type: `integer`):

Only contracts with a published value of at least this many Australian dollars. Contracts with no published value are left out when this is set. 0 means no minimum.

## `states` (type: `array`):

Only contracts with a supplier in one of these states or territories. Leave empty for all of them.

## `unspscPrefixes` (type: `array`):

Only contracts with a category code starting with one of these UNSPSC prefixes, e.g. "43" for information technology. Leave empty for all categories.

## `buyerContains` (type: `string`):

Only contracts whose government buyer name contains this text (case-insensitive), e.g. "Department of Defence". Leave empty for all buyers.

## `maxResults` (type: `integer`):

Stop after this many contracts. Each one is charged as one result.

## `failIfEmpty` (type: `boolean`):

For monitoring: mark the run as failed when nothing is found. Leave off for normal use.

## Actor input object example

```json
{
  "daysAhead": 90,
  "keywords": [],
  "minValueAud": 0,
  "states": [],
  "unspscPrefixes": [],
  "buyerContains": "",
  "maxResults": 1000,
  "failIfEmpty": false
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("ausgovdata/au-contracts-ending").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("ausgovdata/au-contracts-ending").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call ausgovdata/au-contracts-ending --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ausgovdata/au-contracts-ending"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/3b9Q7X7l9955tbQpu/builds/rRiM4JXQop83hh5Oh/openapi.json