/comprar/tenders/search

POST /api/comprar/tenders/search

Price: 20 credits

Search Argentine federal procurement processes on COMPR.AR (goods and services) or CONTRAT.AR (public works) by name, file number, buying service and unit, procedure, status, category, opening date range and operation type. Returns one row per process: number, file number, name, procedure, status, opening date, buying unit and buying service.

How to use it

At least one filter is required. `buying_service` and `buying_unit` take a row's `buying_service_code` and `buying_unit_code` (`105`, `14/2`), and a buying service code is the same on both portals. Pass `number` and `portal` to comprar/tenders for items, schedule, requirements and the purchase orders with supplier CUIT and amount.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• portal string — Portal to search (default: "comprar"; one of: "comprar", "contratar")
• query string nullable — Words of the process name (examples: "equipos informaticos"; minLength: 3)
• file_number string nullable — Part of the administrative file number (examples: "EX-2020-60431513"; minLength: 3)
• buying_service string nullable — Buying service (SAF) code (examples: "105"; minLength: 1)
• buying_unit string nullable — Buying unit (UOC) code within the buying service (examples: "14/2"; minLength: 1)
• procedure_type string nullable — Procurement procedure (one of: "public_tender", "private_tender", "public_contest", "private_contest", "direct_contracting", "public_auction", "price_comparison")
• status string nullable — Status of the process (one of: "published", "opening", "under_evaluation", "ready_to_award", "pre_awarded", "pending_award", "pending_contract_document", "pending_allocation", "pending_analysis", "awarded", "awarded_with_contract_documents", "contract_documents_authorized", "authorized_pending_registration", "void", "cancelled", "auction_pending_start", "auction_running")
• category string nullable — Category of the purchase (examples: "INFORMATICA", "ALIMENTOS"; minLength: 1)
• opening_from string nullable — Earliest opening date (examples: "2024-03-01")
• opening_to string nullable — Latest opening date (examples: "2024-03-05")
• operation_type string nullable — Operation type (one of: "rent", "sale", "concession")
• sort string — Order of the rows (default: "number"; one of: "number", "name", "procedure_type", "opening_date", "status")
• count integer required — Max number of processes to return (min: 1; max: 1000)

Response

• @type string (default: "ComprarTenderSummary")
• number string required
• portal string required
• file_number string nullable
• name string nullable
• procedure_type string nullable
• status string nullable
• opening_at integer nullable
• buying_unit_code string nullable
• buying_unit string nullable
• buying_service_code string nullable
• buying_service string nullable
• country string (default: "AR")

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.