LeetCode problem solutions and discussion posts API

Use the LeetCode problem solutions and discussion posts API to retrieve programming reference entries, topic tags, published summaries, author information, comment counts and record identities and titles as structured JSON from LeetCode. Supply record slug in the query; optionally select sort option and search words to set the requested scope. Use these results to find community explanations and connect problem references with relevant solution discussions. The documented source-page link form identifies the requested entry directly and lets you reuse an existing source-page reference. Continue with the returned next_page as page; a null value marks the last page. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Problem slug, title or leetcode.com/problems/<slug>/ link.
Optional parameters (10)
hot (default), most_votes or most_recent.
Comma-separated language or topic tag slugs (python3, java, cpp, hash-table...).
Only posts matching these words.
Posts per page (max 50).
Page number.
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON are not supported.
With output=csv|ndjson: the top-level list to turn into rows (e.g. `reviews`), or `.` for the whole object as one row.

Sample response

{
  "cached": false,
  "count": 1,
  "credits_used": 1,
  "fetched_at": "2026-11-19T12:29:39.594Z",
  "items": [
    {
      "author": {
        "avatar": "https://assets.leetcode.com/users/leetcode/avatar_1568224780.png",
        "name": "LeetCode",
        "username": "leetcode"
      },
      "comments": 3973,
      "created_at": "2021-06-25T02:47:00+00:00",
      "downvotes": 361,
      "has_video": true,
      "official": true,
      "reactions": {
        "thumbs_down": 361,
        "upvote": 5141
      },
      "slug": "two-sum-by-leetcode-kwuq",
      "summary": "Video Solution   Solution Article Approach 1: Brute Force Algorithm The brute force approach is simple. Loop through each element x and find if there is another",
      "tags": [],
      "title": "Two Sum",
      "top_level_comments": 2831,
      "topic_id": 127810,
      "updated_at": "2021-06-25T02:47:00+00:00",
      "upvotes": 5141,
      "url": "https://leetcode.com/problems/two-sum/solutions/127810/two-sum-by-leetcode-kwuq",
      "views": 14531684
    }
  ],
  "next_page": 2,
  "order": "hot",
  "page": 1,
  "q": null,
  "slug": "two-sum",
  "tags": [],
  "total": 3000
}

Response result

Response structure

Inferred from examples
  • cachedboolean
  • countinteger
  • credits_usedinteger
  • fetched_atstring
  • itemsobject[]
    • authorobject
      • avatarstring
      • namestring
      • usernamestring
    • commentsinteger
    • created_atstring
    • downvotesinteger
    • has_videoboolean
    • officialboolean
    • reactionsobject
      • thumbs_downinteger
      • upvoteinteger
    • slugstring
    • summarystring
    • tagsunknown[]
    • titlestring
    • top_level_commentsinteger
    • topic_idinteger
    • updated_atstring
    • upvotesinteger
    • urlstring
    • viewsinteger
  • next_pageinteger
  • orderstring
  • pageinteger
  • qnull
  • slugstring
  • tagsunknown[]
  • totalinteger

Loading related APIs…

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use LeetCode problem solutions and discussion posts API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.