# /moeqa/programmes/search

`POST /api/moeqa/programmes/search`

Price: 20 credits

Search the academic programmes that Qatar's Ministry of Education and Higher Education recognises at higher education institutions in Qatar, by programme name, institution, college, sector and suspension status. Each record carries the English and Arabic programme name, its college, the institution with its id and website, the academic year of the list and whether the programme is suspended, with the note.

## How to use it

Text filters match words anywhere in the English or Arabic name and combine with each other; pass institution_id from moeqa/institutions/search to list one institution.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (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 programmes to skip (default: 0; min: 0)
- `name` (string, nullable) — Words of the programme name in English or Arabic, each matched anywhere in it, ignoring letter case (examples: "Computer Science", "Master of Business Administration", "هندسة")
- `institution_id` (string, nullable) — Institution id (examples: "qatar-university", "hamad-bin-khalifa-university")
- `institution` (string, nullable) — Words of the institution name in English or Arabic (examples: "Georgetown", "Lusail")
- `college` (string, nullable) — Words of the college name in English or Arabic (examples: "College of Engineering")
- `sector` (string, nullable) — Section of the ministry list the institution is in (one of: "public", "private", "teaching_location")
- `is_suspended` (boolean, nullable) — Whether the programme is marked suspended

## Response

### 200 — Successful Response

- `@type` (string) (default: "MoeqaProgramme")
- `name` (string, required)
- `name_ar` (string, nullable)
- `is_suspended` (boolean) (default: false)
- `status_note` (string, nullable)
- `status_note_ar` (string, nullable)
- `college` (string, nullable)
- `college_ar` (string, nullable)
- `college_website_url` (string, nullable)
- `institution_id` (string, required)
- `institution_name` (string, required)
- `institution_name_ar` (string, nullable)
- `institution_website_url` (string, nullable)
- `sector` (string, required) (one of: "public", "private", "teaching_location")
- `academic_year` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-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.

