/gojep/opened_bids

POST /api/gojep/opened_bids

Price: 5 credits

The opened bids of one Jamaican government procurement competition on GOJEP (gojep.gov.jm) by resource id: title, status, closing and bid opening dates, and every bid with its envelope, lot, supplier name, bid id and financial value in JMD.

How to use it

Takes the `id` of a gojep/opened_tenders/search or gojep/tenders/search row; a competition whose bids are not opened yet answers 412. A value the procuring entity did not disclose comes back empty. `tender_url` is not filled; pass `id` to gojep/tenders for the competition itself.

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 competition or its opened-bids page URL (examples: "10563689", "https://www.gojep.gov.jm/epps/eawarding/showDetailsOpenedTender.do?resourceId=10563689"; minLength: 1)

Response

• @type string (default: "GojepBidOpening")
• id string required
• name string nullable
• status string nullable
• published_at integer nullable
• cycles array (default: [])
  • @type string (default: "EppsCycle")
  • number integer nullable
  • closing_at integer nullable
  • opening_at integer nullable
• bids array (default: [])
  • @type string (default: "GojepBid")
  • cycle integer nullable
  • lot_name string nullable
  • envelope string nullable
  • supplier_name string nullable
  • bid_id string nullable
  • financial_value number nullable
  • currency string nullable
• tender_url string nullable
• country string (default: "JM")
• 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 opened competition 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.