# NZ GETS Government Tenders Scraper (`jungle_synthesizer/nz-gets-government-tenders-scraper`) Actor

Scrape New Zealand government tenders from GETS: open and closed RFx notices with agency, dates, UNSPSC category, region, contact and full overview.

- **URL**: https://apify.com/jungle_synthesizer/nz-gets-government-tenders-scraper.md
- **Developed by:** [BowTiedRaccoon](https://apify.com/jungle_synthesizer) (community)
- **Categories:** Lead generation, Business
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 record scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## NZ GETS Government Tenders Scraper

Get New Zealand government tender notices from GETS, the Government Electronic Tenders Service, as clean structured data. Every record is a full notice: the buying agency, notice type, UNSPSC category, region, open and close dates, the published overview and the procurement contact.

Use it to monitor new opportunities, feed a bid pipeline, build a lead list of buying agencies, or track what NZ public bodies have bought and when.

### What you get

| Field              | Description                                                 |
|--------------------|-------------------------------------------------------------|
| `rfx_id`           | GETS RFx ID, the notice's unique identifier                 |
| `reference_number` | The agency's own reference (null when none was given)       |
| `title`            | Notice title                                                |
| `agency`           | Buying organisation                                         |
| `rfx_type`         | Notice type code such as RFT, RFP, RFQ, RFI or NOI          |
| `rfx_type_name`    | Notice type spelled out                                     |
| `status`           | `open` or `closed`                                          |
| `category`         | Primary UNSPSC category name                                |
| `category_code`    | Primary UNSPSC category code                                |
| `categories`       | Every UNSPSC category on the notice, as `code - name`       |
| `region`           | Regions the notice covers, comma-separated                  |
| `published_date`   | Open date, `YYYY-MM-DD`, New Zealand local date             |
| `close_date`       | Close date, `YYYY-MM-DD`, New Zealand local date            |
| `close_time`       | Close time, 24-hour `HH:mm`, New Zealand local time         |
| `close_at`         | Close moment as ISO-8601 with the New Zealand UTC offset    |
| `tender_coverage`  | Coverage, for example Sole Agency                           |
| `description`      | The overview text published with the notice                 |
| `contact_name`     | Named procurement contact                                   |
| `contact_email`    | Procurement contact email (null when the agency lists none) |
| `detail_url`       | The notice page on GETS                                     |

Sparse fields are genuinely sparse on the source: some agencies publish no reference number, and some list a phone number but no email.

### Input

| Input          | Description                                                                                     |
|----------------|-------------------------------------------------------------------------------------------------|
| `maxItems`     | Maximum number of notices to return.                                                            |
| `tenderStatus` | `open` for current tenders, `closed` for past ones, or both. Leave empty for open tenders only. |

Closed tenders are returned most recent first.

#### Example input

```json
{
    "maxItems": 100,
    "tenderStatus": ["open"]
}
```

#### Example output

```json
{
    "rfx_id": "35056905",
    "reference_number": "PC00623",
    "title": "Ngā Taupuni restroom refurbishment",
    "agency": "Porirua City Council",
    "rfx_type": "RFP",
    "status": "open",
    "category_code": "72121100",
    "region": "Wellington",
    "published_date": "2026-10-01",
    "close_date": "2026-10-30",
    "close_time": "12:00",
    "close_at": "2026-10-30T12:00:00+13:00",
    "contact_name": "Danielle Lewis",
    "contact_email": "procurement@poriruacity.govt.nz"
}
```

### Notes

- Only what GETS publishes without an account is returned. Tender documents sit behind a GETS login and are not included.
- Dates are New Zealand local time; use `close_at` for an unambiguous moment.
- Run it daily with `open` to catch new notices as they appear.

# Actor input Schema

## `sp_intended_usage` (type: `string`):

What will this data feed? E.g. lead lists, KYB checks, price tracking.

## `sp_improvement_suggestions` (type: `string`):

Provide any feedback or suggestions for improvements.

## `sp_contact` (type: `string`):

We'll personally help with your use case. No spam.

## `resumeCursor` (type: `string`):

Leave empty for a fresh crawl. To CONTINUE a previous run where it stopped — without paying again for records you already received — paste the `resumeCursor` value from that run's Output (the run's OUTPUT key). Resume promptly: the previous run's data expires with your account's retention window (free tier: your ~10 most recent runs).

## `maxItems` (type: `integer`):

Maximum number of tender notices to return

## `tenderStatus` (type: `array`):

Which notices to collect: currently open tenders and/or closed (historical) tenders. Leave empty for open tenders only.

## Actor input object example

```json
{
  "sp_contact": "Share your email here...",
  "maxItems": 10,
  "tenderStatus": [
    "open"
  ]
}
```

# Actor output Schema

## `results` (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 = {
    "sp_contact": "Share your email here...",
    "maxItems": 10,
    "tenderStatus": [
        "open"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("jungle_synthesizer/nz-gets-government-tenders-scraper").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 = {
    "sp_contact": "Share your email here...",
    "maxItems": 10,
    "tenderStatus": ["open"],
}

# Run the Actor and wait for it to finish
run = client.actor("jungle_synthesizer/nz-gets-government-tenders-scraper").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 '{
  "sp_contact": "Share your email here...",
  "maxItems": 10,
  "tenderStatus": [
    "open"
  ]
}' |
apify call jungle_synthesizer/nz-gets-government-tenders-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jungle_synthesizer/nz-gets-government-tenders-scraper"
        }
    }
}
```

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/MjOik9Fnbxe7RAimn/builds/fAPz42OUcovziv2Sh/openapi.json
