POST /api/ched/programs
Price: 10 credits
Get one CHED-authorised degree programme from the Philippine Qualifications Register by its Details URL, confirmed live against the register: 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
Pass the Details URL from a ched/programs/search result to re-read that one programme and confirm it is still in the register; the search already returns the same fields, so use this only to verify a single record live.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)program string required — The Details URL of a programme, as returned in a CHED PhQuaR search result (examples: "https://phquar.ched.gov.ph/?page_id=747&detDegree=Bachelor%20of%20Arts&detMajor=English&detUII=1002&detHei=The%20Adelphi%20College%20Inc.&detRegion=01%20-%20Ilocos%20Region")@type string (default: "ChedProgram")degree string requiredmajor string nullableremarks string nullablepqf_level string nullablepsced string nullableauthorization_type string nullableauthorization_number string nullablestatus string nullableeffectivity string nullablephaseout string nullablequalifications_instrument string nullablehei_id string nullablehei_name string nullablehei_former_names string nullableregion string nullablehei_address string nullablehei_email string nullablehei_website string nullableurl 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 — This programme is no longer in the register under that Details URL 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.