DEV Community article

One DEV article's details: title, summary, link, canonical link, dates (published, edited, crossposted, last comment), reading time, comment and reaction counts, tags, language, images, series id, AI disclosure, author and organization. The article text is returned only with include=body (body_markdown and body_html); include=reactions adds reaction_counts, the count per reaction type (like, unicorn, exploding_head, raised_hands, fire, readinglist).

Every response includes credits_used: the credits this call cost.

Parameters

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

Example

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

import os, requests

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