/gets/tenders/search

POST /api/gets/tenders/search

Price: 10 credits

Search New Zealand government tender notices on GETS by title words, overview words, agency reference, buyer organisation, status, regions, UNSPSC segment categories and the open, close and award date ranges. Each result carries the RFx id, reference, title, tender type, open date and buyer organisation.

How to use it

At least one filter is required; an empty form matches nothing. Results are newest-first and one query serves at most 2000 notices, so narrow a wide query with `published_from`/`published_to` slices to reach an older corpus. `status=awarded` lists completed notices and `awarded_from`/`awarded_to` bound their award date; the supplier names, overview and close date live on gets/tenders, keyed by `id`. Several `regions` widen the match to notices covering any of them.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tender_title string nullable — Words matched in the tender title (examples: "road maintenance"; minLength: 1)
• overview string nullable — Words matched in the notice overview text (examples: "pedestrian crossing"; minLength: 1)
• reference string nullable — Substring of the agency's own reference number (examples: "14983"; minLength: 1)
• organisation_id string nullable — GETS organisation id of the buyer (examples: "81246", "159743")
• status string nullable — Notice status (one of: "published", "late", "closed", "awarded", "cancelled")
• regions array — Regions the notice covers, any of the listed (default: []; one of: "new_zealand", "international", "auckland", "bay_of_plenty", "canterbury", "chatham_islands", "gisborne", "hawkes_bay", "manawatu_wanganui", "marlborough", "nelson", "northland", "otago", "southland", "taranaki", "tasman", "waikato", "wellington", "west_coast"; examples: ["auckland"])
• categories array — UNSPSC segment codes of the notice (default: []; examples: ["43000000"], ["72000000","81000000"])
• published_from string nullable — Earliest open date (examples: "2026-09-01")
• published_to string nullable — Latest open date (examples: "2026-09-21")
• closed_from string nullable — Earliest close date (examples: "2026-09-01")
• closed_to string nullable — Latest close date (examples: "2026-10-31")
• awarded_from string nullable — Earliest award date (examples: "2026-01-01")
• awarded_to string nullable — Latest award date (examples: "2026-06-30")
• count integer required — Max number of results (min: 1; max: 2000)
• offset integer — How many matches to skip before the first returned row (default: 0; min: 0; max: 1999)

Response

• @type string (default: "GetsTenderSummary")
• id string required
• reference string nullable
• tender_type string nullable
• tender_type_code string nullable
• published_at integer nullable
• buyer object nullable
  • @type string (default: "GetsBuyer")
  • name string required
  • code string nullable
  • id string nullable
• country string (default: "NZ")
• url string required

Errors

• 422 — No filter was given, a date was not YYYY-MM-DD, or a category code is not a UNSPSC segment. Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No GETS notice matched those filters. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.