POST /api/emec/specializations/search
Price: 20 credits
Search Brazilian specialisation (lato sensu postgraduate) courses in the e-MEC register by institution, state, municipality, course name, CINE study area, modality and status, ordered by course code.
Specialisation (lato sensu) courses of Brazil's official register, one record per course with its offer municipalities in `locations`; with `state` or `municipality_code` set, `locations` holds only the matching ones. `name` matches text inside the course name as written or in lower, upper, sentence or title case, accents as in the name. `institution` takes the e-MEC code from emec/institutions/search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of specialisation courses to return (min: 1; max: 1000)institution string nullable — e-MEC institution (IES) code offering the course (examples: "423")state string nullable — Brazilian state (UF) where the course is offered (one of: "AC", "AL", "AM", "AP", "BA", "CE", "DF", "ES", "GO", "MA", "MG", "MS", "MT", "PA", "PB", "PE", "PI", "PR", "RJ", "RN", "RO", "RR", "RS", "SC", "SE", "SP", "TO")municipality_code string nullable — IBGE municipality code where the course is offered (examples: "4307005"; pattern: ^\d{7}$)name string nullable — Text contained in the course name (examples: "Gestão", "saúde mental"; minLength: 1)cine_area_code string nullable — CINE study-area code of the course; '4' and '04' both match the courses stored under either spelling (examples: "04", "09"; pattern: ^\d{1,3}$)modality string nullable — Teaching modality (one of: "Presencial", "EAD", "Semipresencial")status string nullable — Register status of the course (one of: "Ativo", "Inativo")@type string (default: "EmecSpecialization")id string requiredname string nullablemodality string nullablestatus string nullableseat_count integer nullableworkload_hours integer nullableduration_months integer nullablecine_area_code string nullablecine_area string nullableinstitution object nullable@type string (default: "EmecSpecializationInstitution")id string nullablename 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 — The entity was not found, or a precondition failed 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.