POST /api/emec/courses
Price: 20 credits
Get a Brazilian undergraduate course from the e-MEC register by its course code: name, degree, modality, status, authorised seats, workload, OCDE and CINE areas, the offering institution and every municipality where it is offered.
One undergraduate course by its e-MEC code, the `id` emec/courses/search returns. `locations` lists every municipality where the course is offered; `institution.id` opens the institution in emec/institutions.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)course string required — e-MEC undergraduate course code (examples: "1704146", "18443")@type string (default: "EmecCourse")id string requiredname string nullabledegree string nullablemodality string nullablestatus string nullableauthorized_seat_count integer nullableworkload_hours integer nullableocde_area string nullablecine_area_code string nullablecine_area string nullableinstitution object nullable@type string (default: "EmecCourseInstitution")id string nullablename string nullableadministrative_category string nullableacademic_organization string nullablelocations array (default: [])@type string (default: "EmecLocation")municipality_code string nullablemunicipality string nullablestate string nullableregion 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 undergraduate course 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.