# /arce/tenders/search

`POST /api/arce/tenders/search`

Price: 20 credits

List Uruguayan public procurement publications on comprasestatales.gub.uy: open calls, awards or every call, filtered by buying body and unit, procedure, budget family, call number and year, award outcome, awarded supplier document and a date range on deadline, publication, modification or award validity. Returns the publication summary with buyer, object and dates per row.

## How to use it

There is no free-text search: narrow by `buyer_id` (the inciso code, 12 is Ministerio de Salud Pública, 29 is ASSE), `procedure`, `category` and a date range, then read `description`. Rows carry no amount; take `id` into arce/tenders for items, contacts and, on awarded calls, the unit prices and suppliers. `award_outcome` and `supplier_document` only apply with `status: "awarded"`.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `status` (string, required) — Which publications to list (one of: "open", "awarded", "all")
- `buyer_id` (integer, nullable) — Inciso code of the buying body (examples: 12, 29; min: 1; max: 99)
- `buyer_unit_id` (integer, nullable) — Executing unit code inside the inciso (examples: 76; min: 1)
- `procedure` (string, nullable) — Procurement procedure (one of: "AO", "CI", "CD", "CE", "CO", "CR", "CM", "DT", "LA", "LP", "EI", "CP", "DI", "LL", "LI", "LN", "PR", "PE", "SI", "VC", "VD", "VA", "VL", "VE", "VR")
- `category` (string, nullable) — Budget family of the goods or services (one of: "2", "3", "4", "5", "6", "10", "12")
- `year` (integer, nullable) — Year of the call number (examples: 2026; min: 2000; max: 2100)
- `number` (string, nullable) — Call number within the year (examples: "15913", "D195902"; minLength: 1)
- `award_outcome` (string, nullable) — Outcome of the award resolution (one of: "1", "2", "3", "4", "5", "6", "7", "8")
- `supplier_document_type` (string, nullable) — Kind of identity document of the awarded supplier (one of: "C", "E", "G", "N", "P", "R", "T", "X")
- `supplier_document` (string, nullable) — Identity document number of the awarded supplier (examples: "217098540014"; minLength: 1)
- `date_type` (string) — Which date the range applies to (default: "PUB"; one of: "ROF", "PUB", "MOD", "VAD")
- `date_from` (string, nullable) — Start of the date range (examples: "2026-09-17")
- `date_to` (string, nullable) — End of the date range (examples: "2026-09-17")
- `sort` (string) — Order of the rows (default: "deadline_asc"; one of: "deadline_asc", "deadline_desc", "published_asc", "published_desc", "modified_asc", "modified_desc")
- `count` (integer, required) — Max number of publications to return (min: 1; max: 1000)

## Response

### 200 — Successful Response

- `@type` (string) (default: "ArceTenderSummary")
- `id` (string, required)
- `ocid` (string, nullable)
- `procedure` (string, nullable)
- `number` (string, nullable)
- `year` (integer, nullable)
- `buyer` (object, nullable)
  - `@type` (string) (default: "ArceOrganization")
  - `id` (string, nullable)
  - `name` (string, nullable)
- `buyer_unit` (string, nullable)
- `description` (string, nullable)
- `deadline_at` (integer, nullable)
- `published_at` (integer, nullable)
- `modified_at` (integer, nullable)
- `country` (string) (default: "UY")
- `url` (string, required)
- `record_url` (string, nullable)

## Errors

### 422 — Validation Error

A paired parameter is missing its partner, or an award filter was used outside status awarded

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.