POST /api/prozorro/contracts/search
Price: 20 credits
Search Prozorro procurement contracts by keyword, buyer or supplier EDRPOU and signing date, newest first or by value; each row carries the contract number, status, buyer, suppliers and contract value.
Use supplier_edrpou to list what a company has won and signed_from/signed_to to bound the signing date. A row's tender_id opens the parent tender through prozorro/tenders, where the awards carry the winning supplier's address and contact.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of contracts to return (min: 1; max: 1000)offset integer — How many contracts to skip before the first returned one (default: 0; min: 0; max: 9999)q string nullable — Keyword in the contract title or number (examples: "Starlink"; minLength: 1)buyer_edrpou array nullable — Buyer EDRPOU codes, any of (examples: ["45712019"])supplier_edrpou array nullable — Supplier EDRPOU codes, any of (examples: ["2722924140"])signed_from string nullable — Earliest signing date, inclusive (examples: "2026-01-01")signed_to string nullable — Latest signing date, inclusive (examples: "2026-09-22")sort_by string — Sort key (default: "signed_at"; one of: "signed_at", "amount")sort_order string — Sort direction (default: "desc"; one of: "desc", "asc")@type string (default: "ProzorroContractSummary")id string requiredtender_id string nullablestatus string nullablebuyer object nullable@type string (default: "ProzorroOrganization")name string nullablename_en string nullableidentifier object nullable@type string (default: "ProzorroIdentifier")scheme string nullableid string nullablelegal_name string nullablelegal_name_en string nullableurl string nullableaddress object nullable@type string (default: "ProzorroAddress")street string nullablelocality string nullableregion string nullablepostal_code string nullablecountry_name string nullablecontact object nullable@type string (default: "ProzorroContact")name string nullablename_en string nullableemail string nullabletelephone string nullablefax string nullableurl string nullableavailable_language string nullableadditional_contacts array (default: [])@type string (default: "ProzorroContact")name string nullablename_en string nullableemail string nullabletelephone string nullablefax string nullableurl string nullableavailable_language string nullablekind string nullablescale string nullablesuppliers array (default: [])@type string (default: "ProzorroOrganization")name string nullablename_en string nullableidentifier object nullable@type string (default: "ProzorroIdentifier")scheme string nullableid string nullablelegal_name string nullablelegal_name_en string nullableurl string nullableaddress object nullable@type string (default: "ProzorroAddress")street string nullablelocality string nullableregion string nullablepostal_code string nullablecountry_name string nullablecontact object nullable@type string (default: "ProzorroContact")name string nullablename_en string nullableemail string nullabletelephone string nullablefax string nullableurl string nullableavailable_language string nullableadditional_contacts array (default: [])@type string (default: "ProzorroContact")name string nullablename_en string nullableemail string nullabletelephone string nullablefax string nullableurl string nullableavailable_language string nullablekind string nullablescale string nullablevalue object nullable@type string (default: "ProzorroValue")amount number nullableamount_net number nullablecurrency string nullablevat_included boolean nullablecountry string (default: "UA")url string 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.