/secop/tenders

POST /api/secop/tenders

Price: 10 credits

Colombian SECOP II procurement process by process id or portfolio id: name, description, status, stage, procuring entity and unit, procurement method, contract type, UNSPSC categories, base price, duration, publication, reception and opening dates, supplier counts, the award with its supplier and value, and the suppliers that bid.

How to use it

Takes the `id` or `portfolio_id` of a secop/tenders/search row. `award` is filled once the process is awarded, and `bidders` lists the suppliers that submitted an offer.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — SECOP II process id or portfolio id (examples: "CO1.REQ.11060522", "CO1.BDOS.10636629")

Response

• @type string (default: "SecopTenderDetail")
• id string required
• portfolio_id string nullable
• reference string nullable
• description string nullable
• status string nullable
• status_code string nullable
• stage string nullable
• summary_status string nullable
• visibility string nullable
• buyer object nullable
  • @type string (default: "SecopBuyerRef")
  • id string nullable
  • nit string nullable
  • name string nullable
  • department string nullable
  • city string nullable
  • order string nullable
  • centralization string nullable
  • unit_code string nullable
  • unit_name string nullable
  • unit_city string nullable
• procurement_method string nullable
• method_justification string nullable
• contract_type string nullable
• category string nullable
• additional_categories array (default: [])
• value object nullable
  • @type string (default: "SecopValue")
  • amount number required
  • currency string (default: "COP")
• duration number nullable
• duration_unit string nullable
• lot_count integer nullable
• published_date string nullable
• last_published_date string nullable
• draft_published_date string nullable
• selection_published_date string nullable
• prequalification_planning_date string nullable
• prequalification_selection_date string nullable
• interest_published_date string nullable
• deadline_date string nullable
• opening_date string nullable
• actual_opening_date string nullable
• is_awarded boolean nullable
• award object nullable
  • @type string (default: "SecopAward")
  • id string nullable
  • value object nullable
    • @type string (default: "SecopValue")
    • amount number required
    • currency string (default: "COP")
  • awarded_date string nullable
  • awarder_name string nullable
  • supplier object nullable
    • @type string (default: "SecopSupplierRef")
    • id string nullable
    • nit string nullable
    • name string nullable
    • department string nullable
    • city string nullable
• invited_supplier_count integer nullable
• directly_invited_supplier_count integer nullable
• interested_supplier_count integer nullable
• responding_supplier_count integer nullable
• response_count integer nullable
• external_response_count integer nullable
• offer_response_count integer nullable
• view_count integer nullable
• country string (default: "CO")
• url string nullable
• bidders array (default: [])
  • @type string (default: "SecopBidder")
  • id string nullable
  • nit string nullable
  • name string nullable

Errors

• 422 — The id is not a CO1.REQ or CO1.BDOS identifier 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 SECOP II process with that id 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.