POST /api/ugandagpp/awards/search
Price: 10 credits
Search the best evaluated bidder notices published on the Uganda Government Procurement Portal by financial year, subject of procurement, procuring entity and procurement reference number. Returns the winning provider, the contract price and the notice expiry date per row.
A best evaluated bidder notice names the provider selected for award before a contract is signed; the signed contract itself is in ugandagpp/contracts/search. `reference_number` is an exact match on the procurement reference, `subject` a substring of the subject, `buyer_id` the numeric entity id — a name returns nothing.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)financial_year string nullable — Ugandan financial year (one of: "2016-2017", "2017-2018", "2018-2019", "2019-2020", "2020-2021", "2021-2022", "2022-2023", "2023-2024", "2024-2025", "2025-2026", "2026-2027")subject string nullable — Words in the subject of procurement (examples: "vehicle", "construction"; minLength: 1)buyer_id integer nullable — Procuring entity id as returned by ugandagpp/buyers/search (examples: 386; min: 1)reference_number string nullable — Procurement reference number (examples: "URA/NONCONS/2025-2026/03882"; minLength: 1)count integer required — Max number of notices to return (min: 1; max: 1000)@type string (default: "UgandagppAward")id integer requiredreference_number string nullablesubject string nullablebuyer_name string nullablesupplier_name string nullablecontract_price number nullablecurrency string nullablenotice_expiry_date string nullablecountry string (default: "UG")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 — The entity was not found, or a precondition failed 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.