/qs/rankings/table

POST /api/qs/rankings/table

Price: 20 credits

Read a QS ranking table with its per-indicator scores

How to use it

One call reads a whole QS table, so pass the widest `count` you want rather than paging. `ranking` is the page of one ranking in one year — a different year of the same ranking is a different page. /qs/rankings/filters lists the years it knows about beside the subject ids, city names and ISO-2 country codes the filters here accept, and a year it does not list, such as '/world-university-rankings/2023', is still worth passing. `rank` is the published value and is often a band such as '701-710' or a tie such as '=90'; `rank_order` is the numeric position to sort on. Roughly half the table carries no `overall_score` at all — QS publishes one only for the ranked head — so treat a null there as unpublished rather than zero. `institution_id` is stable across QS years and has no counterpart at any other ranking publisher.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• ranking string — Which ranking table to read: the path or full address of a QS ranking page, or the numeric table id. Every published year and subject has its own page, and /qs/rankings/filters lists the pages of the years it knows about, which are not always all of them. (default: "/world-university-rankings"; examples: "/world-university-rankings", "/world-university-rankings/2026", "/university-subject-rankings/computer-science-information-systems", "4153156"; minLength: 1)
• country string nullable — Keep only institutions in this country, given as its ISO 3166-1 alpha-2 code. /qs/rankings/filters lists the codes this table holds. (examples: "gb", "us"; minLength: 2; maxLength: 2)
• city string nullable — Keep only institutions in this city, named exactly as /qs/rankings/filters prints it. (examples: "Cambridge"; minLength: 1)
• region string nullable — Keep only institutions in this world region, named exactly as /qs/rankings/filters prints it. (examples: "Europe", "Asia"; minLength: 1)
• search string nullable — Keep only institutions whose name matches this text. (examples: "oxford"; minLength: 1)
• study_level string nullable — Keep only institutions offering this level of study. (one of: "bachelors", "masters", "mba", "phd")
• subject string nullable — Keep only institutions teaching this subject, given as the subject id /qs/rankings/filters returns beside its name. (examples: "468"; minLength: 1)
• sort_by string nullable — Re-order the table by published rank, institution name or overall score. (one of: "rank", "university", "overallscore")
• order string — Direction of `sort_by`; ignored when `sort_by` is not given. (default: "asc"; one of: "asc", "desc")
• count integer required — Max number of institutions to return. (examples: 50; min: 1; max: 5000)

Response

• @type string (default: "QsRankedInstitution")
• id string required
• institution_id string nullable
• core_id string nullable
• name string required
• alias string nullable
• profile_url string nullable
• rank string nullable
• rank_order integer nullable
• overall_score number nullable
• country string nullable
• city string nullable
• region string nullable
• image string nullable
• stars integer nullable
• has_advanced_profile boolean (default: false)
• is_dagger_marked boolean (default: false)
• is_redacted boolean (default: false)
• indicators array (default: [])
  • @type string (default: "QsIndicatorScore")
  • pillar string nullable
  • name string required
  • id string nullable
  • score number nullable
  • rank string nullable

Errors

• 422 — 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 — Ranking page not found 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.

Response 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.