/marchesma/tenders/search

POST /api/marchesma/tenders/search

Price: 20 credits

Search Moroccan public procurement notices on the Portail Marocain des Marchés Publics (marchespublics.gov.ma): consultations by keyword, reference, procedure, category, publication window and bid deadline window, or another announcement kind such as final results. Returns one row per notice: id, organisation acronym, reference, subject, public buyer, procedure, category, publication date, bid deadline and places of execution.

How to use it

Consultations are searched across the whole archive unless a window is set; pass today's date as `deadline_from` for notices still open. Pass `id` with `org_acronym` to marchesma/tenders for the full notice.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Keyword to match in the notice (examples: "travaux", "informatique"; minLength: 1)
• reference string nullable — Reference of the consultation (examples: "SK04/2026/CFR"; minLength: 1)
• announcement_type string — Kind of announcement (default: "annonce_consultation"; one of: "annonce_information", "annonce_consultation", "annonce_resultat_definitif", "annonce_extrait_pv", "annonce_rapport_achevement", "annonce_decision_resiliation", "annonce_rapport_presentation")
• procedure_type string nullable — Procurement procedure (one of: "appel_manifestation_interet", "appel_offres_avec_preselection_phase_1", "appel_offres_avec_preselection_phase_2", "appel_offres_ouvert", "appel_offres_ouvert_simplifie", "appel_offres_restreint", "ppp_prequalification_phase_1", "ppp_prequalification_phase_2", "ppp_preselection_phase_1", "ppp_preselection_phase_2", "concours_phase_2", "concours_architectural", "concours_phase_1", "consultation_architecturale_negociee_phase_1", "consultation_architecturale_negociee_phase_2", "consultation_architecturale_negociee_sans_publicite", "consultation_architecturale_ouverte", "consultation_architecturale_ouverte_simplifiee", "consultation_architecturale_restreinte", "demande_cotation_ouverte_banques_multilaterales", "demande_cotation_restreinte_banques_multilaterales", "dialogue_competitif_phase_1", "dialogue_competitif_phase_2", "dialogue_competitif_phase_3", "enchere_electronique_inversee", "marche_negocie_avec_publicite_prealable_phase_1", "marche_negocie_avec_publicite_prealable_phase_2", "marche_negocie_sans_publicite_prealable")
• category string nullable — Main category of the purchase (one of: "travaux", "fournitures", "services")
• published_from string nullable — Earliest publication date (format: date; examples: "2026-09-01")
• published_to string nullable — Latest publication date (format: date; examples: "2026-09-15")
• deadline_from string nullable — Earliest bid submission deadline (format: date; examples: "2026-09-25")
• deadline_to string nullable — Latest bid submission deadline (format: date; examples: "2026-12-31")
• count integer required — Max number of notices to return (min: 1; max: 1000)

Response

• @type string (default: "MarchesmaTenderSummary")
• id string required
• org_acronym string required
• reference string nullable
• name string nullable
• buyer_name string nullable
• procedure_type string nullable
• procedure_code string nullable
• category string nullable
• published_date string nullable
• submission_deadline_at integer nullable
• execution_locations array (default: [])
• has_environmental_clauses boolean (default: false)
• country string (default: "MA")
• url string required

Errors

• 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.