POST /api/ugandagpp/contracts/search
Price: 20 credits
Search the signed contracts published on the Uganda Government Procurement Portal by subject of procurement and procuring entity. Returns each contract with its supplier, amount, signing and completion dates, the procurement plan entry and the winning bid submission.
The feed is a 2015-2019 slice of the register: rows come newest signing date first (page 1 signed 2019-03, the last page 2015-10) and nothing signed after 2019-03 is on it; there is no sort, date or provider filter, so narrow with `subject` and `buyer_id`, then read `signing_date`. `bid_invitation_id` is the id for ugandagpp/tenders. `final_contract_value` is filled only once the contract has closed out. `currency` is null when the source states an `exchange_rate` other than 1 without naming the currency.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)subject string nullable — Words in the subject of procurement (examples: "vehicle", "road"; minLength: 1)buyer_id integer nullable — Procuring entity id as returned by ugandagpp/buyers/search (examples: 386; min: 1)count integer required — Max number of contracts to return (min: 1; max: 1000)@type string (default: "UgandagppContract")id integer requiredawarded_contract_id integer nullablebid_invitation_id integer nullableocid string nullablebuyer object nullable@type string (default: "UgandagppPde")id integer requiredname string nullableabbreviation string nullablecategory string nullableaddress string nullablesupplier object nullable@type string (default: "UgandagppProvider")id integer requiredname string requiredcontract_amount number nullablefinal_contract_value number nullablecurrency string nullable (default: "UGX")exchange_rate number nullablefinal_contract_value_currency string nullablefinal_contract_value_exchange_rate number nullablesigning_date string nullablecommencement_date string nullablecompletion_date string nullableactual_completion_date string nullablecontract_manager string nullableperformance_rating integer nullableis_terminated boolean nullableis_direct_procurement boolean nullableis_emergency_procurement boolean nullablehas_sub_contractors boolean nullablefinancial_year string nullableplan_entry object nullable@type string (default: "UgandagppPlanEntry")id integer requiredsubject string nullableprocurement_method object nullable@type string (default: "UgandagppProcurementMethod")id integer requiredcode string nullablename string nullabledescription string nullablebidding_period_days integer nullableprocurement_category object nullable@type string (default: "UgandagppProcurementCategory")id integer requiredcode string nullablename string nullableocds_code string nullablefunding_source object nullable@type string (default: "UgandagppFundingSource")id integer requiredname string nullableestimated_amount number nullablecurrency string (default: "UGX")quantity integer nullablerationale string nullablehas_reservation_schemes boolean nullablebid_submission object nullable@type string (default: "UgandagppBidSubmission")id integer requiredbid_invitation_id integer nullableocid string nullableprovider object nullable@type string (default: "UgandagppProvider")id integer requiredname string requiredis_best_evaluated_bidder boolean nullableis_approved boolean nullableis_joint_venture boolean nullablenationality string nullablenationality_status string nullableread_out_price number nullablecurrency string nullable (default: "UGX")received_by string nullablereceived_date string nullablereservation_beneficiary string nullablefinancial_year string nullablecreated_at integer nullablecountry string (default: "UG")created_at integer nullable422 — 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.