POST /api/emec/institutions
Price: 1 credit
Get a Brazilian higher-education institution from the e-MEC register by its institution code: name, acronym, public or private category, academic organisation, community and confessional flags, the register's philanthropic code, seat municipality with its IBGE code, state and register status.
One institution of Brazil's official higher-education register by its e-MEC code, the `id` that emec/institutions/search returns and the `institution.id` on every course. Use emec/courses/search or emec/specializations/search with the same code for what it teaches.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)institution string required — e-MEC institution (IES) code (examples: "423", "1")@type string (default: "EmecInstitution")id string requiredname string nullableacronym string nullablecategory string nullableacademic_organization string nullableis_community boolean nullableis_confessional boolean nullablephilanthropic_code string nullablemunicipality_code string nullablemunicipality string nullablestate string nullablestatus 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 has that e-MEC code 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.