/rues/companies

POST /api/rues/companies

Price: 1 credit

Get a Colombian company record from RUES by internal id, NIT or registration number

How to use it

Get full RUES registry details for a Colombian company by its internal RUES id, NIT, or matrícula.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string nullable — Internal RUES record id (examples: "390000015351")
• nit string nullable — Tax identification number (NIT) without verification digit (examples: "890903938")
• matricula string nullable — Commercial registration number (matrícula mercantil) (examples: "0008396404")

Response

• @type string (default: "RuesCompany")
• id string required
• chamber_code string nullable
• chamber string nullable
• registration_number string nullable
• name string required
• sigla string nullable
• identification_class string nullable
• nit string nullable
• identification_number string nullable
• dv string nullable
• ciiu_primary_code string nullable
• ciiu_primary_description string nullable
• ciiu_secondary_code string nullable
• ciiu_secondary_description string nullable
• ciiu3_code string nullable
• ciiu3_description string nullable
• ciiu4_code string nullable
• ciiu4_description string nullable
• registration_date string nullable
• renewal_date string nullable
• last_renewed_year string nullable
• validity_date string nullable
• cancellation_date string nullable
• cancellation_reason string nullable
• company_type_code string nullable
• company_type string nullable
• legal_organization string nullable
• registration_category string nullable
• status string nullable
• updated_at string nullable
• is_social_enterprise boolean (default: false)
• is_law_1780 boolean (default: false)
• is_bic_company boolean (default: false)
• is_transport boolean (default: false)
• has_asset_forfeiture boolean (default: false)
• certificate_url string nullable

Errors

• 422 — The request body did not validate 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 RUES record found for the given identifier 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.