/dncp/buyers

POST /api/dncp/buyers

Price: 1 credit

Procuring entity registered on the Paraguayan DNCP portal by SICP code: name, institution type, government level, entity type and the parent entity of a dependent unit.

How to use it

The SICP code is the number after `DNCP-SICP-CODE-` in any `buyer.id` of dncp/tenders/search; pass it as `buyer_id` there to list the entity's processes. `member_of` names the parent entity of a dependent unit (a hospital under the ministry, a faculty under its university) and is empty on a top-level entity. The entity record carries no contact details or address.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — SICP code of the procuring entity or its OCDS party id (examples: "306", "DNCP-SICP-CODE-306"; minLength: 1)

Response

• @type string (default: "DncpBuyer")
• id string required
• sicp_code string required
• name string required
• legal_name string nullable
• country string (default: "PY")
• identifier object nullable
  • @type string (default: "DncpIdentifier")
  • scheme string nullable
  • id string nullable
  • legal_name string nullable
• institution_type string nullable
• level string nullable
• party_type string nullable
• member_of array (default: [])
  • @type string (default: "DncpOrganization")
  • id string nullable
  • name string nullable
• updated_at integer nullable

Errors

• 422 — The id is not a numeric SICP 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 SICP 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.