/philgeps/tenders

POST /api/philgeps/tenders

Price: 5 credits

One open Philippine government bid notice from PhilGEPS (notices.philgeps.gov.ph) by reference number: title, notice type, procuring entity and client agency, solicitation number, procurement mode and rules, classification and category, approved budget, delivery area and period, status, description, line items, contact, pre-bid conference time and venue, publish, update and closing dates.

How to use it

Takes the `id` of a philgeps/tenders/search row. A notice that has closed returns 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 — Bid notice reference number or notice page URL (examples: "13242682", "https://notices.philgeps.gov.ph/GEPSNONPILOT/Tender/SplashBidNoticeAbstractUI.aspx?menuIndex=3&refID=13242682"; minLength: 1)

Response

• @type string (default: "PhilgepsTender")
• id string required
• name string nullable
• notice_type string nullable
• buyer_name string nullable
• client_agency string nullable
• solicitation_number string nullable
• procurement_mode string nullable
• procurement_rules string nullable
• classification string nullable
• category string nullable
• approved_budget number nullable
• currency string (default: "PHP")
• delivery_area string nullable
• delivery_period string nullable
• status string nullable
• description string nullable
• line_items array (default: [])
  • @type string (default: "PhilgepsLineItem")
  • item_number string nullable
  • name string nullable
  • description string nullable
  • quantity number nullable
  • unit string nullable
  • budget number nullable
• other_information string nullable
• contact string nullable
• contact_name string nullable
• contact_email string nullable
• bid_supplements_count integer nullable
• document_requests_count integer nullable
• published_date string nullable
• updated_at integer nullable
• closing_at integer nullable
• pre_bid_conference_at integer nullable
• pre_bid_conference_venue string nullable
• created_by string nullable
• created_date string nullable
• country string (default: "PH")
• 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 open bid notice under that reference number 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.