/ghaneps/tenders/search

POST /api/ghaneps/tenders/search

Price: 20 credits

Search the tenders advertised on the Ghana Electronic Procurement System (ghaneps.gov.gh) by keyword, sorted by any column. Returns one row per tender: resource id, title, procuring entity, bid submission deadline, procurement method, status, publication date and notice PDF.

How to use it

Only advertised tenders are listed; requests for quotation and single-source procurements appear in ghaneps/opened_tenders/search and ghaneps/awards/search. Pass `id` to ghaneps/tenders for the full notice or, once the bids are opened, to ghaneps/opened_bids for bidders and prices; a tender still in bid submission answers 412 there.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Word, word prefix or exact phrase (examples: "school"; minLength: 1)
• sort string nullable — Field to order the tenders by (one of: "published_at", "submission_deadline_at", "name", "buyer_name", "procurement_method", "status")
• order string — Direction of the sort (default: "desc"; one of: "desc", "asc")
• count integer required — Max number of tenders to return (min: 1; max: 5000)

Response

• @type string (default: "GhanepsTenderSummary")
• id string required
• name string nullable
• buyer_name string nullable
• submission_deadline_at integer nullable
• procurement_method string nullable
• status string nullable
• published_at integer nullable
• notice_url string nullable
• country string (default: "GH")
• url string required

Errors

• 422 — The request body did not validate 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 — The entity was not found, or a precondition failed 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.