LeetCode problem list · LeetCode API

GET https://api.api.sh/leetcode/v1/problems

1 credit / call reference try it in the playground →

LeetCode problems with the problem-set filters: number, title, slug, link, difficulty, acceptance rate, premium flag, topic tags and whether an official (video) solution exists. total is the number of matches. Pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

name	type	description
`q`	string	Search words in the title or the problem number.
`difficulty`	easy \| medium \| hard	Difficulty. Example: `hard`
`tags`	string	Topic tag slugs, comma-separated (all must match), e.g. `dynamic-programming,tree`. Example: `dynamic-programming`
`category`	algorithms \| database \| shell \| concurrency \| javascript \| pandas	Problem category.
`premium`	true \| false	`true`: premium problems only; `false`: free only.
`order_by`	id \| ac_rate \| difficulty \| frequency	Sort field (default: problem number).
`sort`	asc \| desc	`asc` (default) or `desc` (with order_by).
`page`	integer	Page number (default 1).
`limit`	integer	Results per page (default 50, max 100).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/leetcode/v1/problems" \
  -H "x-api-key: $APISH_KEY"

import os, requests

res = requests.get(
    "https://api.api.sh/leetcode/v1/problems",
    params={},
    headers={"x-api-key": os.environ["APISH_KEY"]},
    timeout=120,
)
res.raise_for_status()
data = res.json()

const url = new URL("https://api.api.sh/leetcode/v1/problems");


const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json();

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.