POST /api/snies/institutions
Price: 20 credits
Get one Colombian higher-education institution from SNIES by its SNIES code: name, status, NIT, main campus or branch, legal nature, sector, academic character, domicile address and phone, website, creation norm, accreditation, mission, programme counts, its directors with their appointment dates, and the places it covers.
Use this to read one institution behind an `id` from snies/institutions/search; its programmes are listed by snies/programs/search with `institution` set to the same code.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)institution string required — SNIES code of the institution (examples: "1101", "1208"; minLength: 1; maxLength: 6)@type string (default: "SniesInstitution")id string requiredparent_id string nullablename string nullablestatus string nullablenit string nullablecampus_type string nullablelegal_nature string nullablesector string nullableacademic_character string nullabledepartment string nullablemunicipality string nullableaddress string nullablephone string nullablecreation_norm_type string nullablecreation_norm_issuer string nullablecreation_norm_number string nullablecreation_norm_date integer nullableactive_program_count integer nullableagreement_program_count integer nullablewebsite string nullableis_high_quality_accredited boolean nullableaccreditation_date integer nullableaccreditation_resolution string nullableaccreditation_validity_years integer nullablemission string nullabledirectors array (default: [])@type string (default: "SniesInstitutionDirector")first_name string nullablelast_name string nullablerole string nullableappointment_act string nullableappointment_norm_date integer nullablestart_date integer nullableend_date integer nullablelocations array (default: [])@type string (default: "SniesInstitutionLocation")coverage_type string nullabledepartment string nullablemunicipality string nullable422 — 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 institution with that SNIES code exists in SNIES. 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.