# /mtender/tenders/search

`POST /api/mtender/tenders/search`

Price: 10 credits

Search MTender procurements by phrase, buyer IDNO, buyer or delivery region, procedure type and status, CPV code, estimated value range and publication, enquiry, submission or delivery dates, most recently modified first; each row carries the ocid, title, description, procedure type and status, the buyer's name and region and the estimated value.

## How to use it

q matches the exact phrase in the title or description, so prefer one or two words in Romanian. cpv takes full codes such as 45453000-7; a parent class code does not include its children. The buyer's IDNO, the CPV codes and the deadlines are not in the rows — pass the row's ocid to mtender/tenders.

## 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 tenders to return (min: 1; max: 1000)
- `offset` (integer) — How many tenders to skip before the first returned one (default: 0; min: 0; max: 100000)
- `q` (string, nullable) — Phrase in the title or description (examples: "Reparație boiler"; minLength: 1)
- `buyer_idno` (array, nullable) — Buyer IDNO codes, any of (examples: ["1013620006366"])
- `buyer_region` (array, nullable) — Buyer regions, any of (one of: "chisinau", "balti", "bender", "anenii_noi", "basarabeasca", "briceni", "cahul", "cantemir", "calarasi", "causeni", "cimislia", "criuleni", "donduseni", "drochia", "dubasari", "edinet", "falesti", "floresti", "glodeni", "hincesti", "ialoveni", "leova", "nisporeni", "ocnita", "orhei", "rezina", "riscani", "singerei", "soroca", "straseni", "soldanesti", "stefan_voda", "taraclia", "telenesti", "ungheni", "gagauzia", "transnistria")
- `delivery_region` (array, nullable) — Delivery regions, any of (one of: "chisinau", "balti", "bender", "anenii_noi", "basarabeasca", "briceni", "cahul", "cantemir", "calarasi", "causeni", "cimislia", "criuleni", "donduseni", "drochia", "dubasari", "edinet", "falesti", "floresti", "glodeni", "hincesti", "ialoveni", "leova", "nisporeni", "ocnita", "orhei", "rezina", "riscani", "singerei", "soroca", "straseni", "soldanesti", "stefan_voda", "taraclia", "telenesti", "ungheni", "gagauzia", "transnistria")
- `procedure_type` (array, nullable) — Procedure types, any of (one of: "microValue", "smallValue", "openTender", "restrictedTender", "negotiatedProcedure", "directCallOff", "requestForQuotations", "openFA", "directAward")
- `status` (array, nullable) — Procedure statuses, any of (one of: "published", "negotiation", "submission", "qualification", "clarification", "tendering", "auction", "awarding", "suspended", "awarded", "cancelled", "unsuccessful")
- `cpv` (array, nullable) — CPV codes, any of (examples: ["45453000-7"])
- `amount_from` (number, nullable) — Minimum estimated value in MDL (examples: 1000000; min: 0)
- `amount_to` (number, nullable) — Maximum estimated value in MDL (examples: 2000000; min: 0)
- `published_from` (string, nullable) — Earliest publication date, inclusive (examples: "2026-09-01")
- `published_to` (string, nullable) — Latest publication date, inclusive (examples: "2026-09-22")
- `enquiry_from` (string, nullable) — Earliest enquiry deadline, inclusive (examples: "2026-06-01")
- `enquiry_to` (string, nullable) — Latest enquiry deadline, inclusive (examples: "2026-06-30")
- `deadline_from` (string, nullable) — Earliest bid submission deadline, inclusive (examples: "2026-06-01")
- `deadline_to` (string, nullable) — Latest bid submission deadline, inclusive (examples: "2026-06-30")
- `delivery_from` (string, nullable) — Earliest delivery period start, inclusive (examples: "2026-06-01")
- `delivery_to` (string, nullable) — Latest delivery period end, inclusive (examples: "2026-12-31")

## Response

### 200 — Successful Response

- `@type` (string) (default: "MtenderTenderSummary")
- `id` (string, required)
- `ocid` (string, required)
- `description` (string, nullable)
- `status` (string, nullable)
- `stage` (string, nullable)
- `procedure_type` (string, nullable)
- `procedure_ownership` (string, nullable)
- `buyer` (object, nullable)
  - `@type` (string) (default: "MtenderPartyRef")
  - `id` (string, nullable)
  - `name` (string, nullable)
- `buyer_region` (string, nullable)
- `value` (object, nullable)
  - `@type` (string) (default: "MtenderValue")
  - `amount` (number, nullable)
  - `amount_net` (number, nullable)
  - `currency` (string, nullable)
- `modified_at` (integer, nullable)
- `country` (string) (default: "MD")
- `url` (string, required)

## 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.