/comprasmx/tenders/search

POST /api/comprasmx/tenders/search

Price: 20 credits

Search Mexico's federal procurement procedures on ComprasMX by name, procedure number, case file, stage, status, law, contract and procedure type, national or international character, participation mode, state, consolidated, SME-reserved and externally financed purchases, publication date and bid opening date, newest first, with the buying unit, state, procedure type, status and key dates of each.

How to use it

stage groups statuses: open procedures accept bids, in_progress ones are being opened or evaluated, concluded ones were awarded, cancelled or deserted. Pass a row id to comprasmx/tenders for the full procedure, and to comprasmx/tenders/contracts for the awarded contracts with their line items.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of results (min: 1; max: 5000)
• offset integer — Number of matching results to skip (default: 0; examples: 0, 5000; min: 0; max: 1000000)
• number string nullable — Procedure number or its beginning (examples: "LA-07-110-007000999-T-699-2026")
• file_code string nullable — Case file code (examples: "E-2026-00105657")
• stage string nullable — Stage of the procedure (one of: "open", "in_progress", "concluded")
• statuses array nullable — Procedure statuses to include (one of: "clarifications", "answering_questions", "follow_up_questions", "current", "opening", "award_decision", "evaluation", "pending_opening", "suspended", "awarded", "partially_awarded", "cancelled", "deserted"; minItems: 1)
• law string nullable — Law the procedure is conducted under (one of: "laassp", "lopsrm", "lapp", "credex", "ceep")
• contract_type string nullable — Type of contract (one of: "acquisitions", "leases", "services", "public_works", "works_related_services")
• procedure_type string nullable — Procurement procedure (one of: "direct_award", "invitation_three", "public_tender", "framework_call_off")
• character string nullable — National or international character (one of: "national", "international_treaties", "international_open")
• participation string nullable — How bids are submitted (one of: "electronic", "mixed", "in_person")
• states array nullable — States where the contract is placed (examples: ["MX-CMX","MX-JAL"]; minItems: 1)
• is_consolidated_purchase boolean nullable — Only consolidated purchases
• is_sme_exclusive boolean nullable — Reserved for micro, small and medium firms
• has_external_credit boolean nullable — Financed with external credit
• published_from string nullable — Earliest publication date, inclusive (examples: "2026-09-01")
• published_to string nullable — Latest publication date, inclusive (examples: "2026-09-10")
• opening_from string nullable — Earliest bid opening date, inclusive (examples: "2026-10-01")
• opening_to string nullable — Latest bid opening date, inclusive (examples: "2026-10-31")

Response

• @type string (default: "ComprasmxTenderSummary")
• id string required
• procedure_id string nullable
• number string nullable
• file_code string nullable
• buyer_acronym string nullable
• buying_unit string nullable
• state string nullable
• procedure_type string nullable
• contract_type string nullable
• character string nullable
• status string nullable
• status_detail string nullable
• clarifications_at integer nullable
• opening_at integer nullable
• url string nullable

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.