/marchesma/excluded_suppliers/search

POST /api/marchesma/excluded_suppliers/search

Price: 10 credits

Search the Moroccan register of companies excluded from public procurement on the Portail Marocain des Marchés Publics (marchespublics.gov.ma) by company name, commercial register city and number. Returns one row per exclusion: record id, company name, commercial register number, the public entity that excluded it, reason, start and end dates, scope, and the decision file format and size.

How to use it

With no filter the whole register is returned. An exclusion with no `end_date` has no end set; `scope` tells whether it covers all purchases or only part.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• name string nullable — Part of the company name (examples: "TRAVAUX"; minLength: 1)
• registry_city string nullable — City of the commercial register the company is filed in (one of: "agadir", "alhoceima", "asilah", "azilal", "ben_ahmed", "ben_slimane", "benguerir", "beni_mellal", "berkane", "berrechid", "bouarfa", "boujaad", "boulmane", "casablanca", "chefchaouen", "dakhla", "eljadida", "errachidia", "essaouira", "es_smara", "fes", "fkih_ben_saleh", "guelmim", "guercif", "imintanoute", "inzegane", "kalaa_sraghna", "kasba_tadla", "kenitra", "khemisset", "khenifra", "khouribga", "ksar_kebir", "laayoune", "larache", "marrakech", "meknes", "midelt", "mohamedia", "nador", "ouarzazate", "ouazzane", "oued_zem", "oujda", "rabat", "romani", "safi", "sale", "sefrou", "settat", "sidi_bennour", "sidi_kacem", "sidi_slimane", "souk_larbaa", "tanger", "tantan", "taounate", "taroudante", "tata", "taza", "tetouan", "tiznit", "youssoufia", "zagora", "taourirt", "azrou", "temara", "tinghir", "mechra_bel_ksiri", "tiflet", "targuist", "souk_sebt_ouled_nemma", "driouch", "biougra")
• registry_number string nullable — Commercial register number (examples: "77279"; minLength: 1)
• count integer required — Max number of excluded companies to return (min: 1; max: 500)

Response

• @type string (default: "MarchesmaExcludedSupplier")
• id string nullable
• name string nullable
• registry_number string nullable
• buyer_name string nullable
• reason string nullable
• start_date string nullable
• end_date string nullable
• scope string nullable
• document_format string nullable
• document_size string nullable
• country string (default: "MA")

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.