LeetCode contest

docs menu

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

1 credit / call reference try it in the playground →

One LeetCode contest: title, link, start time, duration, finished flag, premium flag, description and its problems with points.

Every response includes credits_used: the credits this call cost.

Parameters

name	type	description
`slug`required	string	Contest slug or leetcode.com/contest/ link. Example: `weekly-contest-400`

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

Example

curl "https://api.api.sh/leetcode/v1/contest?slug=weekly-contest-400" \
  -H "x-api-key: $APISH_KEY"

import os, requests

res = requests.get(
    "https://api.api.sh/leetcode/v1/contest",
    params={"slug": "weekly-contest-400"},
    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/contest");
url.searchParams.set("slug", "weekly-contest-400");

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.