/placsp/tenders/search

POST /api/placsp/tenders/search

Price: 20 credits

Search the tenders of Spain's Plataforma de Contratación del Sector Público — the state public sector and the regional platforms aggregated into it, below-threshold procurement included — by file number, contracting body, awardee, contract type, status, procedure, processing type, submission method, EU funding, CPV codes, country of execution, publication date, submission deadline and estimated value, with the contract type, status, budget, deadline and contracting body of each tender.

How to use it

A query returns at most its first 200 hits, so narrow a wide search with published_from/published_to, status or buyer_name. Pass the id of a row to placsp/tenders for the estimated value, CPV codes, award result and the published notices and documents, and the buyer id to placsp/buyers for the contracting body's NIF and contact details.

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: 200)
• file_number string nullable — Tender file number (examples: "300/2026/01098"; minLength: 1)
• buyer_name string nullable — Contracting body name (examples: "Ayuntamiento de Madrid"; minLength: 1)
• awardee_name string nullable — Awardee name (examples: "FERROVIAL"; minLength: 1)
• contract_type string nullable — Contract type (one of: "supplies", "services", "works", "special_administrative", "private", "public_services_management", "services_concession", "public_works_concession", "works_concession", "public_private_partnership", "patrimonial")
• status string nullable — Tender status (one of: "prior_notice", "published", "prior_evaluation", "evaluation", "awarded", "partially_awarded", "provisionally_awarded", "resolved", "partially_resolved", "cancelled")
• procedure string nullable — Procurement procedure (one of: "open", "simplified_open", "restricted", "negotiated_with_publicity", "negotiated_without_publicity", "competitive_dialogue", "competitive_negotiation", "innovation_partnership", "derived_from_innovation_partnership", "framework_based", "dynamic_system_based", "design_contest", "internal_rules", "other")
• processing string nullable — Processing type (one of: "ordinary", "urgent", "emergency")
• submission_method string nullable — Offer submission method (one of: "electronic", "manual", "manual_or_electronic")
• eu_funded boolean nullable — Funding by European Union funds
• cpv array nullable — CPV codes, matching their subcodes too (examples: ["45000000"], ["45000000","72000000"]; minItems: 1)
• country string nullable — Country of execution code (examples: "ES")
• published_from string nullable — Earliest publication date, inclusive (examples: "2026-09-01")
• published_to string nullable — Latest publication date, inclusive (examples: "2026-09-10")
• deadline_from string nullable — Earliest submission deadline date, inclusive (examples: "2026-10-01")
• deadline_to string nullable — Latest submission deadline date, inclusive (examples: "2026-10-31")
• value_min number nullable — Minimum estimated value in EUR (examples: 100000; min: 0)
• value_max number nullable — Maximum estimated value in EUR (examples: 200000; min: 0)

Response

• @type string (default: "PlacspTenderSummary")
• id string required
• file_number string nullable
• contract_type string nullable
• contract_subtype string nullable
• status string nullable
• budget_amount number nullable
• currency string (default: "EUR")
• submission_deadline_date string nullable
• buyer object nullable
  • @type string (default: "PlacspBuyerRef")
  • id string nullable
  • name string nullable
  • platform_id string nullable
  • hierarchy string nullable
  • url string nullable
• country string (default: "ES")
• url string required

Errors

• 422 — A search value the platform does not accept, such as an unknown CPV code 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.