POST /api/moeqa/institutions/search
Price: 20 credits
Search the higher education institutions recognised by Qatar's Ministry of Education and Higher Education by name and sector (public, private, teaching location). Each record carries the institution id, its English and Arabic names, website, academic year of the list, its colleges and the number of its recognised and suspended programmes.
Use this to find a Qatari institution and its id; pass the id to moeqa/institutions for its 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)name string nullable — Words of the institution name in English or Arabic, each matched anywhere in it, ignoring letter case (examples: "Qatar University", "Carnegie Mellon", "جامعة قطر")sector string nullable — Section of the ministry list the institution is in (one of: "public", "private", "teaching_location")@type string (default: "MoeqaInstitution")id string requiredname string requiredname_ar string nullablesector string required (one of: "public", "private", "teaching_location")list_position integer nullablewebsite_url string nullableacademic_year string nullableprogramme_count integer (default: 0)suspended_programme_count integer (default: 0)colleges array (default: [])@type string (default: "MoeqaCollege")name string nullablename_ar string nullablewebsite_url string nullableprogramme_count integer (default: 0)422 — 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.