Dev.to Feed API
The Dev.to front page and its popular windows, with the top comments already attached to each card.
GET /v1/dev-to/feed1 credit Failed requests are free
About this endpoint
GET /v1/dev-to/feed takes a window of home (the default), latest, week, month, year or infinity for all time. The response returns window, a page of cards and the usual page block. Each card has id, url, slug, title, tags, publishedAt, editedAt, readingTimeMinutes, reactionsCount, commentsCount, coverImage, videoUrl, communityId, aiDisclosure, isPinned, experienceLevel, experienceLevelVotes, contextNote, flareTag, the author and the organization.
Each card also carries topComments, the comments the feed shows under the post, with commentId, id, url, createdAt, bodyHtml and the comment author. That makes the feed route a faster way to collect a front page and its conversation than joining the article and comment routes. page is 1 to 2000 and this route has no limit parameter. A page past the end of the feed returns an empty cards list with hasMore false.
Dev.to Feed API FAQ
Which window should I use?
home for the default front page, latest for strictly newest posts, or week, month, year and infinity for the most popular posts over that period. The chosen value is echoed in the window field.
How many credits does a feed page 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. Each paginated page is a separate billed request.
Are comments included?
Yes, to the depth the feed shows them, in topComments on each card. For the full thread, use GET /v1/dev-to/article/comments with the card id.
What do experienceLevel and contextNote mean?
experienceLevel is the reading level readers voted from 1 to 10, with experienceLevelVotes giving the number of voters. contextNote is the editors' one-line note as HTML, or null when there is none.