DEV Community articles
Articles on DEV (dev.to) by tag, tags, author or organization, as the feed, latest, top of the last N days, fresh or rising: id, title, summary, link, canonical link, dates, reading time, comment and reaction counts, tags, language, cover image, author (name, username, Twitter and GitHub handles) and organization. Titles and summaries only, not the article text. 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 |
|---|---|---|
tag | string | One tag, e.g. javascript. Example: javascript |
tags | string | Several tags, comma-separated (any match). |
tags_exclude | string | Tags to leave out, comma-separated. |
username | string | Articles by this user or organization username. |
collection_id | string | Articles of a series (collection id). |
sort | default | latest | top | fresh | rising | default (feed), latest, top (most reactions in top_days), fresh or rising. Example: top |
top_days | integer | With sort=top: the number of days (default 7). Example: 7 |
page | integer | Page number (default 1). |
limit | integer | Results per page (default 30, max 100). |
Every endpoint also takes fresh, raw, fields (see lean responses and caching).
Example
curl "https://api.api.sh/devto/v1/articles?tag=javascript" \
-H "x-api-key: $APISH_KEY" import os, requests
res = requests.get(
"https://api.api.sh/devto/v1/articles",
params={"tag": "javascript"},
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/articles");
url.searchParams.set("tag", "javascript");
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).