# /procurement/tenders/search

`POST /api/procurement/tenders/search`

Price: 225 credits

Search government tenders and procurement notices across 81 national procurement portals in 78 countries and the EU's Tenders Electronic Daily in one call, 93 countries in all, by source, country, keyword and publication date. Every notice comes back in one shape: source, country, the source's own id, title, buyer, publication time, submission deadline, stated value with currency, link and status. Newest publication first, notices without a publication time last.

## How to use it

id is the named source's own notice identifier, which most sources' own tender endpoints take for the full record. A source that cannot apply a requested filter, or does not answer, is named in X-Warning.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `count` (integer, required) — Max number of results (min: 1; max: 1000)
- `sources` (array) — Sources to search; with countries, the union of both (default: []; one of: "appal", "arce", "austender", "bdegp", "bhtender", "boamp", "bonfirebb", "bonfirebs", "canadabuys", "ccgp", "cejn", "comprar", "comprasal", "comprasmx", "contractsfinder", "cppp", "cyeproc", "dgcp", "dncp", "doffin", "dubaiesupply", "enabavki", "enarocanje", "eopbg", "ezamowienia", "findatender", "gebiz", "gem", "gets", "ghaneps", "gojep", "goszakup", "guatecompras", "gyeprocure", "hilma", "jpportal", "kenyappip", "kimdis", "marchesbj", "marchesci", "marchescm", "marchesga", "marchesma", "marchesmg", "marchesml", "marchesmr", "marchesne", "marchessn", "marchestg", "mercadopublico", "mrgovil", "mtender", "mtetenders", "nocopo", "oeffentlichevergabe", "omantender", "panamacompra", "philgeps", "placsp", "ppcc", "ppra", "procurett", "prozorro", "riigihanked", "saetenders", "seace", "secop", "sercop", "sicap", "sicop", "ted", "tenderned", "thaiegp", "twpcc", "uaemof", "udbud", "ugandagpp", "uvo", "uzex", "vneps", "zakupkikg", "zppa"; examples: ["boamp","ted"])
- `countries` (array) — ISO 3166-1 alpha-2 countries to search (default: []; one of: "AE", "AL", "AR", "AT", "AU", "BB", "BD", "BE", "BG", "BH", "BJ", "BS", "CA", "CH", "CI", "CL", "CM", "CN", "CO", "CR", "CY", "CZ", "DE", "DK", "DO", "EC", "EE", "ES", "FI", "FR", "GA", "GB", "GH", "GR", "GT", "GY", "HR", "HU", "IE", "IL", "IN", "IS", "IT", "JM", "JP", "KE", "KG", "KZ", "LI", "LR", "LT", "LU", "LV", "MA", "MD", "ME", "MG", "MK", "ML", "MR", "MT", "MX", "NE", "NG", "NL", "NO", "NZ", "OM", "PA", "PE", "PH", "PK", "PL", "PT", "PY", "RO", "SE", "SG", "SI", "SK", "SN", "SV", "TG", "TH", "TT", "TW", "UA", "UG", "UY", "UZ", "VN", "ZA", "ZM"; examples: ["FR","DE"], ["KE"])
- `keyword` (string, nullable) — Words to search for (examples: "hospital"; minLength: 1)
- `published_from` (string, nullable) — Earliest publication date, inclusive (format: date; examples: "2026-09-01")
- `published_to` (string, nullable) — Latest publication date, inclusive (format: date; examples: "2026-09-28")

## Response

### 200 — Successful Response

- `@type` (string) (default: "ProcurementTender")
- `source` (string, required) — Source the notice comes from (one of: "appal", "arce", "austender", "bdegp", "bhtender", "boamp", "bonfirebb", "bonfirebs", "canadabuys", "ccgp", "cejn", "comprar", "comprasal", "comprasmx", "contractsfinder", "cppp", "cyeproc", "dgcp", "dncp", "doffin", "dubaiesupply", "enabavki", "enarocanje", "eopbg", "ezamowienia", "findatender", "gebiz", "gem", "gets", "ghaneps", "gojep", "goszakup", "guatecompras", "gyeprocure", "hilma", "jpportal", "kenyappip", "kimdis", "marchesbj", "marchesci", "marchescm", "marchesga", "marchesma", "marchesmg", "marchesml", "marchesmr", "marchesne", "marchessn", "marchestg", "mercadopublico", "mrgovil", "mtender", "mtetenders", "nocopo", "oeffentlichevergabe", "omantender", "panamacompra", "philgeps", "placsp", "ppcc", "ppra", "procurett", "prozorro", "riigihanked", "saetenders", "seace", "secop", "sercop", "sicap", "sicop", "ted", "tenderned", "thaiegp", "twpcc", "uaemof", "udbud", "ugandagpp", "uvo", "uzex", "vneps", "zakupkikg", "zppa")
- `country` (string, nullable) — ISO 3166-1 alpha-2 country of the buyer
- `id` (string, required) — The source's own notice identifier
- `key` (string, required) — Source and id joined, unique across sources
- `name` (string, nullable) — Notice title
- `buyer` (string, nullable) — Contracting authority name
- `published_at` (integer, nullable) — Publication time, unix seconds
- `deadline_at` (integer, nullable) — Submission deadline, unix seconds
- `value` (number, nullable) — Amount the notice states: estimate, budget or award
- `currency` (string, nullable) — Currency of value
- `url` (string, nullable) — Notice page or document on the source
- `status` (string, nullable) — Status or stage label as the source spells it

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

The entity was not found, or a precondition failed

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.