/gojep/tenders

POST /api/gojep/tenders

Price: 5 credits

One Jamaican government procurement competition on GOJEP (gojep.gov.jm) by resource id: procuring entity, procurement type, method and technique, award criteria, CPV codes, PPC categories, lots, funding, the publication, clarification, submission, opening and award dates, and on awarded competitions the actual spend in JMD.

How to use it

Takes the `id` of a gojep/tenders/search row or the `tender_id` of a gojep/awards/search row. Restricted, single-source, RFQ and emergency competitions and archived ones answer 412, which covers the gojep/opened_tenders/search rows; gojep/opened_bids still returns their bidders.

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 page URL (examples: "10575133", "https://www.gojep.gov.jm/epps/cft/prepareViewCfTWS.do?resourceId=10575133"; minLength: 1)

Response

• @type string (default: "GojepTender")
• id string required
• name string nullable
• reference string nullable
• project_reference string nullable
• buyer object nullable
  • @type string (default: "EppsBuyerRef")
  • id string nullable
  • name string required
• summary string nullable
• procurement_type string nullable
• services_subtype string nullable
• procurement_method string nullable
• procurement_technique string nullable
• procurement_policy string nullable
• competition_level string nullable
• procurement_tier string nullable
• award_criteria string nullable
• stages_count integer nullable
• is_framework boolean nullable
• framework_end_at integer nullable
• cpv_codes array (default: [])
  • @type string (default: "EppsCode")
  • code string nullable
  • name string nullable
• ppc_categories array (default: [])
  • @type string (default: "EppsCode")
  • code string nullable
  • name string nullable
• works_grade string 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
• has_e_catalogue boolean nullable
• funding_source string nullable
• funding_providers array (default: [])
  • @type string (default: "EppsCode")
  • code string nullable
  • name string nullable
• performance_country string nullable
• petroleum_indicator string nullable
• special_treatment string nullable
• tender_round string nullable
• retender_reason string nullable
• is_correspondence_audited boolean nullable
• is_ppc_endorsed boolean nullable
• published_at integer nullable
• site_visit_at integer nullable
• clarification_end_at integer nullable
• original_submission_deadline_at integer nullable
• submission_deadline_at integer nullable
• opening_at integer nullable
• planned_evaluation_end_at integer nullable
• planned_award_at integer nullable
• awarded_at integer nullable
• actual_spend number nullable
• currency string (default: "JMD")
• 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 public 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.