Dev.to Article Details API
The fields that live on a post's page: series navigation, co-authors and comment reaction counts.
GET /v1/dev-to/article/details1 credit Failed requests are free
About this endpoint
GET /v1/dev-to/article/details takes exactly one of id or url and returns details with the fields the plain post route does not carry: articleId, url, isPublished, isScheduled, coAuthorIds, series and commentsOnPage.
series has its id, title, url, partsCount and a parts array with position, title and url, so you can walk a multi-part tutorial. commentsOnPage gives each comment's id, numeric numericId and reactionsCount. When Dev.to hides a post's page, listedOnSite is false and the detail fields are null or empty, but the post itself is still available from /v1/dev-to/article.
Dev.to Article Details API FAQ
When should I use this instead of the article route?
Use this route when you need series navigation, co-authors, publication state or per-comment reaction counts. For the post and its body, /v1/dev-to/article is enough.
How many credits does a details lookup cost?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.
What does listedOnSite false mean?
The post exists but its page is hidden, so the page-only fields are not available. lookupStatus is still found, and the post data is still returned by the article and comment routes.
How do I use the series parts?
details.series.parts is ordered by position from 1. Each part has a title and a URL. When the post is not in a series, series is null.