POST /api/marchessn/tenders/search
Price: 10 credits
Search calls for tenders published on the Senegal national public procurement portal by subject words, kind of purchase, class of contracting authority and publication date, with the reference, subject, contracting authority, publication date, submission deadline and category. Newest publication first.
id opens the notice with its procurement method and text through marchessn/tenders; a row without category_code has no notice page on the portal, so it carries no url and marchessn/tenders answers 412 for it. reference often equals tender_reference on a marchessn/awards record.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of results (min: 1; max: 5000)keyword string nullable — Words in the subject (examples: "route"; minLength: 1)notice_type string nullable — Kind of purchase (one of: "intellectual_services", "works", "supplies", "services", "public_service_concession")buyer_type string nullable — Class of contracting authority (one of: "central_government", "local_authority", "public_institution", "state_company", "agency", "decentralised_service", "other")date_from string nullable — Earliest publication date (examples: "2026-01-01")date_to string nullable — Latest publication date (examples: "2026-06-30")@type string (default: "MarchessnTenderRow")id string requiredreference string nullablenotice_type string nullablesubject string nullablebuyer_name string nullablepublished_date string nullablesubmission_deadline string nullablecategory_code string nullablecategory string nullableurl 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.