/gyeprocure/tenders

POST /api/gyeprocure/tenders

Price: 1 credit

One procurement opportunity advertised on the Government of Guyana notice board (eprocure.gov.gy) by project id: the list fields — agency, procurement nature and method, current state, advertisement and bid opening dates, regions — joined to the invitation for bids as text (header, scope, instructions, footer) and its documents.

How to use it

Takes the `id` of a gyeprocure/tenders/search row, in any letter case. A notice that is no longer published answers 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Project id (examples: "PROC-2026-00433"; minLength: 1)

Response

• @type string (default: "GyeprocureTender")
• id string required
• agency string nullable
• agency_code string nullable
• procurement_method string nullable
• procurement_nature string nullable
• procurement_sub_nature string nullable
• estimated_value number nullable
• status string nullable
• advertised_date string nullable
• projected_bid_opening_date string nullable
• actual_bid_opening_date string nullable
• regions array (default: [])
• documents array (default: [])
  • @type string (default: "GyeprocureDocument")
  • name string nullable
  • url string required
• header string nullable
• scope string nullable
• instructions string nullable
• footer string nullable

Errors

• 422 — The id is not a project id such as PROC-2026-00433 Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 — No published procurement opportunity under that id 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 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 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 Wait at least 30 seconds, then retry.

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