# /gojep/awards/search

`POST /api/gojep/awards/search`

Price: 20 credits

Search Jamaican government contract award notices on GOJEP (gojep.gov.jm) by procurement method, procuring entity, contract amount range and notice date range, newest first or sorted by any column. Returns one row per notice: notice id, competition resource id and title, procurement method, procuring entity, contract amount in JMD, notice date and notice PDF.

## How to use it

`buyer_name` matches any part of the name. One competition can carry several notices. The awarded supplier is printed only in the notice PDF; pass `tender_id` to gojep/opened_bids for the bidders. `tender_url` is set on National Competitive Bidding notices only; the other methods have no public tender page and answer 412 on gojep/tenders.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `procurement_method` (string, nullable) — Procurement method (one of: "international_competitive_bidding", "national_competitive_bidding", "restricted_bidding", "single_source", "rfp_with_negotiation", "rfp_without_negotiation", "request_for_quote", "emergency")
- `buyer_name` (string, nullable) — Part of the procuring entity name (examples: "National Health Fund"; minLength: 1)
- `amount_min` (number, nullable) — Lowest contract amount in JMD (examples: 10000000; min: 0)
- `amount_max` (number, nullable) — Highest contract amount in JMD (examples: 1000; min: 0)
- `published_from` (string, nullable) — Earliest notice date (format: date; examples: "2026-09-01")
- `published_to` (string, nullable) — Latest notice date (format: date; examples: "2020-12-31")
- `sort` (string, nullable) — Field to order the notices by (one of: "published_at", "amount", "tender_name", "buyer_name", "procurement_method")
- `order` (string) — Direction of the sort (default: "desc"; one of: "desc", "asc")
- `count` (integer, required) — Max number of award notices to return (min: 1; max: 10000)

## Response

### 200 — Successful Response

- `@type` (string) (default: "GojepAward")
- `id` (string, required)
- `tender_id` (string, nullable)
- `tender_name` (string, nullable)
- `procurement_method` (string, nullable)
- `buyer_name` (string, nullable)
- `amount` (number, nullable)
- `currency` (string) (default: "JMD")
- `published_at` (integer, nullable)
- `notice_url` (string, nullable)
- `tender_url` (string, nullable)
- `country` (string) (default: "JM")

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