Dev.to Trends API
Topics rising on Dev.to, with the questions developers ask about them.
GET /v1/dev-to/trends1 credit Failed requests are free
About this endpoint
GET /v1/dev-to/trends returns trends, hottest first. Each trend has id, name, slug, description, keyQuestions, score, articlesCount, coverImage, firstObservedAt and lastObservedAt. keyQuestions is a list of strings, which makes the route useful for finding what developers are asking about a technology before you read the posts.
Use page and limit to walk the list, up to 1000 trends per request. score and articlesCount can be null when the value is unavailable. Use /v1/dev-to/trend?slug=... for one trend with its top posts.
Dev.to Trends API FAQ
How are trends ordered?
By score, highest first, as Dev.to ranks them. Use page.nextPage to continue without reordering.
How many credits does a trends 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.
What are keyQuestions?
The questions developers are asking about the trend, as plain strings. They are the trend page's own questions, not generated text.
How do I get the posts in a trend?
Call GET /v1/dev-to/trend with the trend id or slug and include=articles. The trend response then carries a page of posts alongside the trend.