POST /api/philgeps/awards
Price: 1 credit
One Philippine government contract award notice from PhilGEPS (notices.philgeps.gov.ph) by award id and bid notice reference number: contract title and amount, award status and reason, award, publish, proceed and contract dates, contract number, funding source, UNSPSC code, the winning suppliers with address and contact, bidders, the awarded line item, the procuring entity, and the source tender with its approved budget and procurement mode. An award whose bidders, reasons or status codes could not be read is served without them and marked by an X-Warning header.
Takes an award id with the reference number of its bid notice, or the award notice page URL alone. One bid notice can have one award per line item, so the same `tender_id` recurs across awards.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)award_id string required — Award id or award notice page URL (examples: "6249175", "https://notices.philgeps.gov.ph/GEPSNONPILOT/R4/R3_AwardNotice_AwardAbstract.html?RefID=12612768&LineItemID=21&OrgID=117744&AwardID=6249175"; minLength: 1)tender_id string nullable — Reference number of the bid notice the award belongs to (examples: "12612768")@type string (default: "PhilgepsAward")id string requiredtender_id string requiredline_item_id string nullablename string nullableaward_type string nullabletype_code string nullablestatus string nullablestatus_id string nullableclassification_code string nullableamount number nullablecurrency string (default: "PHP")previous_award_id string nullableprevious_amount number nullableawarded_date string nullablepublished_date string nullableupdated_date string nullableclosing_date string nullablecontract_number string nullableproceed_date string nullablecontract_start_date string nullablecontract_end_date string nullablehas_notice_to_proceed boolean nullableis_updated boolean nullablefunding_source string nullablefunding_source_id string nullableprocurement_mode_id string nullableunspsc_code string nullableunspsc_description string nullablebidder_count integer nullabledocument_count integer nullableline_item_count integer nullableaward_reason string nullablecancellation_reason string nullabledisapproval_reason string nullablecreated_by string nullablecreated_date string nullableapprover string nullabletender object nullable@type string (default: "PhilgepsAwardTender")id string nullablereference string nullablename string nullableapproved_budget number nullableprocurement_mode string nullableprocurement_rules string nullableclassification string nullablecategory string nullablefunding_source string nullablefunding_instrument string nullabledelivery_area string nullablecontract_duration string nullablecontact_person string nullablecreated_by string nullablealternative_mode_condition string nullableurl string nullablebuyer object nullable@type string (default: "PhilgepsAwardBuyer")id string nullablename string nullableaddress string nullablesuppliers array (default: [])@type string (default: "PhilgepsAwardSupplier")name string nullableaddress string nullablecontact_person string nullabledesignation string nullablebidders array (default: [])@type string (default: "PhilgepsBidder")id string nullablename string nullablecity string nullablerank integer nullableline_item object nullable@type string (default: "PhilgepsAwardLineItem")id string nullableunspsc_code string nullableunspsc_description string nullablename string nullabledescription string nullablequantity number nullableunit string nullableunit_id string nullablebudget number nullablecountry string (default: "PH")url string required422 — 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 award notice under that award id and 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.