Dev.to Search API
Keyword search across Dev.to posts, returned as the same post objects the list routes use.
GET /v1/dev-to/articles/search1 credit Failed requests are free
About this endpoint
GET /v1/dev-to/articles/search takes a required query of 1 to 300 characters and returns matching posts best match first in articles. The search covers post titles, tags and bodies. top limits results to posts from the last N days, and page and limit control the results, up to 1000 rows in one request.
The response also echoes the query you sent and carries the same page block as the other list routes. Each result is the same post object used by /v1/dev-to/articles, with title, url, tags, reactionsCount, commentsCount, readingTimeMinutes, publishedAt and the author, so one parser handles both routes.
Dev.to Search API FAQ
What does the search match?
Post titles, tags and bodies. Send one query string; there is no field-specific syntax. An empty or whitespace-only query is refused.
Why does a very common word return 503?
Very common single words can time out and return 503; add a second word. A 503 is not billed.
How recent can results be?
top accepts 1 to 3650 and keeps posts from the last N days. Omit it to search the whole archive.
How many credits does a search 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 snippets included?
No. Each hit is the full post object used by the list routes, not a snippet. Read the returned url or call the article route for the body.