/secop/buyers

POST /api/secop/buyers

Price: 1 credit

Procuring entity registered on Colombia's SECOP II by its SECOP II code: NIT, name, entity type, registration date, location, contact details and legal representative.

How to use it

Takes the `buyer.id` of a SECOP II process. To list an entity's processes, pass the same code as `buyer_id` of secop/tenders/search.

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 code of the account (examples: "710834128")

Response

• @type string (default: "SecopParty")
• id string required
• nit string nullable
• name string nullable
• organization_type string nullable
• size string nullable
• is_sme boolean nullable
• is_group boolean nullable
• is_active boolean nullable
• is_buyer boolean nullable
• is_supplier boolean nullable
• created_date string nullable
• country string nullable
• department string nullable
• city string nullable
• location_code string nullable
• address string nullable
• email string nullable
• phone string nullable
• fax string nullable
• website string nullable
• category string nullable
• category_description string nullable
• legal_representative object nullable
  • @type string (default: "SecopRepresentative")
  • name string nullable
  • document_type string nullable
  • document_number string nullable
  • email string nullable
  • phone string nullable

Errors

• 422 — The id is not a numeric SECOP II 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 — No procuring entity with that SECOP II code 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.