# /sicop/tenders/search

`POST /api/sicop/tenders/search`

Price: 20 credits

Search Costa Rican public procurement procedures on SICOP by free text, or by title words, purchasing institution, procedure type, procedure number, classification code, open-for-bids state and a publication window. Returns the procedure number, title, state, institution and key dates per row.

## How to use it

Use `keyword` alone for an all-time text search; the other filters work inside a publication window of at most 180 days, which defaults to the last 180 days. Take a row `id` into sicop/tenders for the budget, conditions, lines and documents, and `buyer.id` into sicop/buyers.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `keyword` (string, nullable) — Free-text query over every published procedure (examples: "computadoras"; minLength: 2)
- `buyer_id` (string, nullable) — Purchasing institution id, as in sicop/buyers (examples: "4000042152")
- `procedure_type` (string, nullable) — Procedure type code (one of: "LN", "LI", "LA", "PP", "CD", "CE", "RE", "LY", "LE", "LD", "PE", "SE", "PX")
- `procedure_number` (string, nullable) — Procedure number (examples: "2026LD-000043-0020600006"; minLength: 5)
- `classification_code` (string, nullable) — Goods and services classification code (examples: "43211507"; minLength: 2)
- `open_only` (boolean) — Keep only procedures receiving bids (default: false)
- `published_from` (string, nullable) — Earliest publication date (format: date; examples: "2026-03-01")
- `published_to` (string, nullable) — Latest publication date (format: date; examples: "2026-09-22")
- `count` (integer, required) — Max number of procedures to return (min: 1; max: 1000)

## Response

### 200 — Successful Response

- `@type` (string) (default: "SicopTenderRow")
- `id` (string, required)
- `cartel_no` (string, required)
- `cartel_seq` (string, required)
- `procedure_number` (string, nullable)
- `status` (string, nullable)
- `stage` (string, nullable)
- `buyer` (object, nullable)
  - `@type` (string) (default: "SicopBuyerRef")
  - `id` (string, nullable)
  - `name` (string, nullable)
- `procedure_type` (string, nullable)
- `procedure_type_detail_code` (string, nullable)
- `bid_document_type` (string, nullable)
- `published_at` (integer, nullable)
- `bid_start_at` (integer, nullable)
- `deadline_at` (integer, nullable)
- `opening_at` (integer, nullable)
- `executor_id` (string, nullable)
- `executor_name` (string, nullable)
- `is_secret` (boolean, nullable)
- `is_closed` (boolean, nullable)
- `has_contract_request` (boolean, nullable)
- `country` (string) (default: "CR")

## Errors

### 422 — Validation Error

keyword was combined with other filters, or the publication window is longer than 180 days

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.