/dncp/suppliers

POST /api/dncp/suppliers

Price: 1 credit

Registered supplier on the Paraguayan DNCP portal by RUC: legal name, legal entity type, size and scale, activity types, product categories and catalogue products, sanctions (disqualifications and warnings with their period and events), contact point and address.

How to use it

To list what a supplier won, pass the same RUC as `supplier_id` of dncp/tenders/search with `stage: "Adjudicada"`. `size` is the portal's own MIPYME label and reads `Sin categorizar` for most companies; `scale` is the OCDS code (`sme`, `micro`) where the portal set one. `sanctions[].kind` is `INHABILITACION` (barred for `period`) or `AMONESTACION` (a written warning).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Supplier RUC or its OCDS party id (examples: "80025906-8", "PY-RUC-80025906-8"; minLength: 1)

Response

• @type string (default: "DncpSupplier")
• id string required
• ruc 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
• contact object nullable
  • @type string (default: "DncpContact")
  • name string nullable
  • email string nullable
  • telephone string nullable
  • fax string nullable
  • url string nullable
• address object nullable
  • @type string (default: "DncpAddress")
  • street string nullable
  • locality string nullable
  • region string nullable
  • country_name string nullable
• legal_entity_type string nullable
• size string nullable
• scale string nullable
• activity_types array (default: [])
• activity_type_details string nullable
• categories array (default: [])
  • @type string (default: "DncpCategoryRef")
  • id string required
  • name string nullable
• products array (default: [])
  • @type string (default: "DncpCategoryRef")
  • id string required
  • name string nullable
• sanctions array (default: [])
  • @type string (default: "DncpSanction")
  • id string required
  • kind string nullable
  • status string nullable
  • description string nullable
  • period object nullable
    • @type string (default: "DncpPeriod")
    • start_at integer nullable
    • end_at integer nullable
    • max_extent_at integer nullable
    • duration_days integer nullable
  • events array (default: [])
    • @type string (default: "DncpSanctionEvent")
    • description string nullable
    • date_at integer nullable
• updated_at integer nullable

Errors

• 422 — The id is not a RUC in the NNNNNNNN-N form 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 supplier with that RUC is registered on the portal 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.