/seace/suppliers

POST /api/seace/suppliers

Price: 20 credits

Supplier on Peru's SEACE by RUC: name, legal name, country, contact where published, and how many processes it won, contracts it signed and processes it bid in.

How to use it

Takes `awards[].suppliers[].id` or `tenderers[].id` of a SEACE process; a bare RUC works too. The same id goes to `supplier_id` of seace/contracts/search for its contracts.

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 SEACE party id (examples: "PE-RUC-20303368877", "20303368877")

Response

• @type string (default: "SeaceOrganization")
• id string required
• name string nullable
• legal_name string nullable
• registered_name string nullable
• identifier_scheme string nullable
• identifier string nullable
• ruc string nullable
• roles array (default: [])
• address object nullable
  • @type string (default: "SeaceAddress")
  • street string nullable
  • locality string nullable
  • region string nullable
  • department string nullable
  • country string nullable
• email string nullable
• phone string nullable
• fax string nullable
• website string nullable
• url string nullable
• process_count integer nullable
• contract_count integer nullable
• tendered_process_count integer nullable

Errors

• 422 — The id is not a RUC or SEACE supplier id 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 or bidder with that RUC on SEACE 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.