POST /api/nche/institutions/search
Price: 5 credits
Search the register of Ugandan higher education institutions licensed by the National Council for Higher Education by name, category and district. Each record carries the NCHE institution id, name, category, accreditation status, district and number of accredited programmes; a campus also carries its licence number, accreditation date, status and parent institution.
Use this to find a Ugandan university, college or campus and its NCHE id; pass the id to nche/programmes/search as `institution_id` for its accredited programmes.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of results (min: 1)offset integer — Number of matching institutions to skip (default: 0; min: 0)keyword string nullable — Words of the institution or campus name, each matched anywhere in it, ignoring letter case (examples: "Makerere", "Busitema University")category string nullable — Institution category: university, other degree awarding (odai), other tertiary (oti) or campus (one of: "university", "odai", "oti", "campus")district string nullable — Ugandan district the institution or campus is in, ignoring letter case (examples: "Kampala")@type string (default: "NcheInstitution")id string requiredname string requiredcategory string nullableaccreditation_status string nullabledistrict string nullablecampus_count integer nullableprogramme_count integer nullableaccredited_at integer nullablelicense_number string nullablestatus string nullableparent_institution_id string nullableparent_institution_name string nullableprogrammes_url 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.