DEV Community article comments

docs menu

GET https://api.api.sh/devto/v1/comments

1 credit / call reference try it in the playground →

The comment tree of a DEV article: id, link, date, author (name, username, handles), text and nested replies; with the number of threads and comments.

Every response includes credits_used: the credits this call cost.

Parameters

name	type	description
`article_id`required	string	Numeric article id (from /devto/v1/articles). Example: `4931843`

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

Example

curl "https://api.api.sh/devto/v1/comments?article_id=4931843" \
  -H "x-api-key: $APISH_KEY"

import os, requests

res = requests.get(
    "https://api.api.sh/devto/v1/comments",
    params={"article_id": "4931843"},
    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/devto/v1/comments");
url.searchParams.set("article_id", "4931843");

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.