/ghaneps/tenders

POST /api/ghaneps/tenders

Price: 5 credits

One tender on the Ghana Electronic Procurement System (ghaneps.gov.gh) by resource id: procuring entity, procurement plan reference, procurement type, method and technique, evaluation mechanism, UNSPSC codes, participation fee, bid security, lots, and the publication, clarification, submission, opening and award dates.

How to use it

Takes the `id` of a ghaneps/tenders/search or ghaneps/opened_tenders/search row, or the `tender_id` of a ghaneps/awards/search row. Archived tenders and some awarded ones answer 412. The award amount and supplier are on ghaneps/awards/search, the bidders on ghaneps/opened_bids.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tender_id string required — Resource id of the tender or its page URL (examples: "3636761", "https://www.ghaneps.gov.gh/epps/cft/prepareViewCfTWS.do?resourceId=3636761"; minLength: 1)

Response

• @type string (default: "GhanepsTender")
• id string required
• name string nullable
• reference string nullable
• plan_reference string nullable
• requisition_number string nullable
• buyer object nullable
  • @type string (default: "EppsBuyerRef")
  • id string nullable
  • name string required
• summary string nullable
• procurement_type string nullable
• procurement_method string nullable
• procurement_technique string nullable
• commencement_type string nullable
• evaluation_mechanism string nullable
• stages_count integer nullable
• margin_of_preference string nullable
• is_framework boolean nullable
• framework_end_at integer nullable
• has_postqualification boolean nullable
• unspsc_codes array (default: [])
  • @type string (default: "EppsCode")
  • code string nullable
  • name string nullable
• works_grade string nullable
• participation_fee string nullable
• participation_fee_amount number nullable
• participation_fee_terms string nullable
• bid_security string nullable
• bid_security_amount_type string nullable
• bid_security_value number nullable
• bid_security_currency string nullable
• has_e_catalogue boolean nullable
• has_e_auction boolean nullable
• has_lots boolean nullable
• lots_count integer nullable
• lot_bidding string nullable
• lots array (default: [])
  • @type string (default: "EppsLot")
  • number integer required
  • name string nullable
  • estimated_value number nullable
• published_at integer nullable
• contract_notice_at integer nullable
• clarification_end_at integer nullable
• submission_deadline_at integer nullable
• opening_at integer nullable
• awarded_at integer nullable
• currency string (default: "GHS")
• 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 — No public tender under that resource 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.