POST /api/dgcp/suppliers
Price: 1 credit
Supplier registered with the Dominican DGCP by RPE number or tax document: legal name, legal form, status, SME and MICM certification flags, what it supplies, registration dates, contacts and location.
The RPE is the number after `DO-RPE-` in `suppliers[].id` of dgcp/tenders and in `supplier_rpe` of its contracts. A bare number of nine or more digits is looked up as an RNC or cédula, a shorter one as an RPE; the `DO-RPE-` form is always an RPE.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)id string required — Supplier RPE number, its OCDS party id, or the RNC or cédula it registered with (examples: "16792", "DO-RPE-16792", "101870087"; minLength: 1)@type string (default: "DgcpSupplier")id string requiredrpe string requiredname string requireddocument_type string nullabledocument_number string nullablestatus string nullablegender string nullableperson_type string nullablelegal_form string nullableclassification string nullablebusiness_classification string nullablebusiness_classification_detail string nullableis_sme boolean nullablemicm_certified boolean nullablemicm_certification_expires_at integer nullablenational_producer boolean nullablesupplies string nullablecompany_founded_at integer nullablerpe_registered_at integer nullablecommercial_registry_number string nullablecommercial_registry_at integer nullablecontact_name string nullablecontact_position string nullablecontact_email string nullablecontact_telephone string nullablecontact_mobile string nullablecommercial_email string nullablecommercial_telephone string nullablecommercial_mobile string nullableaddress string nullablecountry string (default: "DO")country_name string nullableregion string nullableprovince string nullablemunicipality string nullablemunicipal_district string nullablecertificate_url string nullable422 — The id is not a number, a DO-RPE- party id or a document number 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 RPE or document number in the register 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.