# /ched/programs/search

`POST /api/ched/programs/search`

Price: 20 credits

Search CHED-authorised degree programmes in the Philippine Qualifications Register by region, institution, programme name, keyword, ownership type and PQF level. Each programme carries its Details URL, degree, major, PQF level, PSCED discipline, authorisation type and number, effectivity and phase-out dates, status, and the offering institution's id, name, former names, region, address, email and website

## How to use it

Set region to walk the whole register one region at a time, or pass hei (the exact institution name), program or keyword to search across all regions; control and level only narrow a result that already has one of those, so do not send them alone. One region returns every programme in it in a single call.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `region` (string, nullable) — CHED administrative region the institution is in (one of: "01 - Ilocos Region", "02 - Cagayan Valley", "03 - Central Luzon", "04 - CALABARZON", "05 - Bicol Region", "06 - Western Visayas", "07 - Central Visayas", "08 - Eastern Visayas", "09 - Zamboanga Peninsula", "10 - Northern Mindanao", "11 - Davao Region", "12 - Soccsksargen", "13 - Nat. Capital Region", "14 - Cordillera Adm. Region", "15 - Bangsamoro Autonomous Region in Muslim Mindanao", "16 - Caraga", "17 - MIMAROPA", "18 - Negros Island Region"; examples: "04 - CALABARZON")
- `hei` (string, nullable) — Exact institution name to list the programmes of (examples: "University of the Philippines Diliman")
- `program` (string, nullable) — Exact degree-programme name to match (examples: "Bachelor of Science in Nursing")
- `keyword` (string, nullable) — Free-text words matched against programme and institution names (examples: "Nursing")
- `control` (string, nullable) — Institution ownership type; narrows the result within another filter (one of: "SUC", "Private", "LUC", "OGS"; examples: "SUC")
- `level` (string, nullable) — PQF / programme level; narrows the result within another filter (one of: "5 (Associate / Diploma)", "6 (Baccalaureate / Bachelor)", "7 (Post Baccalaureate / Master)", "8 (Doctoral and Post Doctoral)"; examples: "6 (Baccalaureate / Bachelor)")
- `count` (integer, required) — Max number of programmes to return (min: 1; max: 5000)

## Response

### 200 — Successful Response

- `@type` (string) (default: "ChedProgram")
- `degree` (string, required)
- `major` (string, nullable)
- `remarks` (string, nullable)
- `pqf_level` (string, nullable)
- `psced` (string, nullable)
- `authorization_type` (string, nullable)
- `authorization_number` (string, nullable)
- `status` (string, nullable)
- `effectivity` (string, nullable)
- `phaseout` (string, nullable)
- `qualifications_instrument` (string, nullable)
- `hei_id` (string, nullable)
- `hei_name` (string, nullable)
- `hei_former_names` (string, nullable)
- `region` (string, nullable)
- `hei_address` (string, nullable)
- `hei_email` (string, nullable)
- `hei_website` (string, nullable)
- `url` (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

No programme in the register matches this combination of filters

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.

