/marchesma/tenders

POST /api/marchesma/tenders

Price: 20 credits

One Moroccan public procurement notice from the Portail Marocain des Marchés Publics (marchespublics.gov.ma) by consultation id and organisation acronym: reference, subject, public buyer, announcement kind, procedure and award method, category, places of execution, estimated value, small-business reservation, activity domains, withdrawal, submission and opening addresses, plans price, provisional guarantee, qualifications, approvals, samples, meeting, site visits, variants, administrative contact, bid deadline or display end, downloadable documents, and on consultations split into lots each lot's title, category, description, estimated value, provisional guarantee, qualifications, approvals, samples, meeting, site visits, variants and small-business reservation. A consultation of more than 200 lots, or one whose per-lot details cannot be retrieved, is served without them and marked by an X-Warning header.

How to use it

An id resolves only together with the `org_acronym` a marchesma/tenders/search row carries; a notice page URL carries both. Closed consultations and result announcements resolve too.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Consultation id or notice page URL (examples: "1041301", "https://www.marchespublics.gov.ma/index.php?page=entreprise.EntrepriseDetailsConsultation&refConsultation=1041301&orgAcronyme=o8p"; minLength: 1)
• org_acronym string nullable — Acronym of the organisation that published the notice (examples: "o8p")

Response

• @type string (default: "MarchesmaTender")
• id string required
• org_acronym string required
• reference string nullable
• name string nullable
• buyer_name string nullable
• announcement_type string nullable
• procedure_type string nullable
• award_method string nullable
• category string nullable
• lots integer nullable
• lot_details array (default: [])
  • @type string (default: "MarchesmaLot")
  • number string nullable
  • name string nullable
  • category string nullable
  • description string nullable
  • estimated_value number nullable
  • provisional_guarantee number nullable
  • qualifications array (default: [])
  • approvals array (default: [])
  • samples string nullable
  • meeting string nullable
  • site_visits string nullable
  • variants_allowed boolean nullable
  • reserved_for_small_business boolean nullable
• execution_locations array (default: [])
• estimated_value number nullable
• currency string (default: "MAD")
• reserved_for_small_business boolean nullable
• activity_domains string nullable
• withdrawal_address string nullable
• submission_address string nullable
• opening_location string nullable
• plans_price number nullable
• provisional_guarantee number nullable
• qualifications array (default: [])
• approvals array (default: [])
• samples string nullable
• meeting string nullable
• site_visits string nullable
• variants_allowed boolean nullable
• contact_name string nullable
• contact_email string nullable
• contact_phone string nullable
• contact_fax string nullable
• submission_deadline_at integer nullable
• display_end_at integer nullable
• documents array (default: [])
  • @type string (default: "MarchesmaDocument")
  • name string nullable
  • size string nullable
  • url string nullable
• 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 — No consultation under that id and organisation acronym 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.