POST /api/hotcoursesabroad/institutions/courses
Price: 5 credits
List the courses of a Hotcourses Abroad institution by its id or page URL, optionally of one study level: course id, name, URL, study level, study mode and duration, start month, tuition fee in local currency and US dollars, delivery and view count.
Courses of one institution in name order. Pass a returned `url` to hotcoursesabroad/courses for the description, entry requirements and every study option. An institution that serves no courses returns an empty list.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)institution string required — Hotcourses Abroad institution id or institution page URL (examples: "910", "https://www.hotcoursesabroad.com/study/uk/school-college-university/kingston-university-london/910/international.html")count integer required — Max number of courses to return (min: 1; max: 240)study_level string nullable — Study level of the courses to return (one of: "undergraduate", "postgraduate", "vocational")@type string (default: "HotcoursesabroadCourseSummary")id string requiredname string nullableurl string nullableinstitution_id string nullableinstitution_name string nullablestudy_level string nullablestudy_level_group string nullablestudy_mode string nullableduration string nullablestarts_at integer nullableis_start_date_expected boolean nullabletuition_fee number nullabletuition_fee_currency string nullabletuition_fee_usd number nullabletuition_fee_period string nullabletuition_fee_text string nullabledelivery string nullableview_count 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 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.