POST /api/usp_fj/programmes
Price: 5 credits
Get one programme of the University of the South Pacific by its alias: programme code, study level, duration, campuses, description, admission requirements, courses with their course codes, programme requirements and its publication and update times.
Pass an `alias` from usp_fj/programmes/search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)programme string required — Programme alias or programme page URL (examples: "bachelor-of-commerce-10", "https://www.usp.ac.fj/programme/master-of-laws/")@type string (default: "UspFjProgramme")id string requiredalias string requiredurl string nullablename string nullablecode string nullablestudy_level string nullableduration string nullablecampuses array (default: [])description string nullableadmission_requirements string nullablecourses string nullableprogramme_requirements string nullablecourse_codes array (default: [])other_sections array (default: [])@type string (default: "UspFjProgrammeSection")title string requiredtext string requiredcreated_at integer nullableupdated_at integer 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 University of the South Pacific lists no programme with this alias. 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.