Open data API

• https://devhunt.org/api/open-data/v1/tools-per-month

  Tools per month by submission date (submitted) and by launch week (launched), pricing model counts and shares, GitHub links, tools marked "not a dev tool", tools removed later.

• https://devhunt.org/api/open-data/v1/categories-per-month

  Tools submitted per month in each category, with the same category list every month, plus shares and the dates categories were added and back-filled.

• https://devhunt.org/api/open-data/v1/changes

  Dated changes to pricing, the submit form, moderation, categories and the launch queue.

• https://devhunt.org/api/open-data/v1

  Index: endpoints, definitions and license.

Add ?complete=true to the per-month endpoints to get complete months only. Every response includes license, licenseUrl, attribution and docsUrl.

curl -s https://devhunt.org/api/open-data/v1/tools-per-month?complete=true

{
  "apiVersion": "1",
  "license": "CC-BY-4.0",
  "licenseUrl": "https://creativecommons.org/licenses/by/4.0/",
  "attribution": "Credit \"DevHunt\" and link to https://devhunt.org",
  "generatedAt": "2026-11-07T18:00:00Z",
  "timezone": "UTC",
  "definitions": { ... },
  "data": [
    { "month": "2024-01", "complete": true, "submitted": 163, "launched": 613,
      "free": 94, "subscription": 44, "oneTime": 25, "paid": 69,
      "freeShare": 0.5767, "paidShare": 0.4233,
      "githubRepo": 45, "githubRepoShare": 0.2761,
      "notDevTool": 0, "removed": 8 },
    ...
  ]
}

month

YYYY-MM, UTC

complete

false for the current month, which is still counting

submitted

tools submitted that month

launched

tools whose launch week started that month

free, subscription, oneTime, paid

pricing model the maker picked, of the tools submitted (paid = subscription + oneTime)

freeShare, paidShare, githubRepoShare

fraction of submitted (0 to 1, 4 decimals), null if nothing was submitted

githubRepo

tools submitted that link a github.com URL

notDevTool

tools marked "not a developer tool" by moderation (from 2026-09)

removed

tools submitted that month that were later deleted or blocked (not in the other counts)

categories-per-month has, for each month, submitted, withCategory (tools with at least one category), counts and shares: one key for each name in categoryNames (AI Coding, AI Agents, MCP, Testing, Security, Monitoring and every other category), always all of them.

Which date does each series use? Can editing a listing change it?

Listed tools by the month they were submitted (products.created_at). Set once when the tool is created; editing a listing does not change it. Listed tools by the month their launch week started (launch_start, UTC). A week that spans two months counts in the month it starts. Only launches that have started are counted. Makers can move their launch week before it starts, and free tools wait in a queue, so this series follows queue rules and pricing more than demand. 2025-01 and 2026-01 hold large batches of queued free tools.

Are removed and blocked tools left out the same way every month?

A tool submitted to DevHunt that is not deleted (by its maker or by DevHunt) and not blocked by moderation. Listings DevHunt adds itself for reference (e.g. Cursor, Claude Code), which never launch, are left out. Deleted tools are left out the same way for every month. Before 2026-09-27 there was no automatic moderation: spam and scams were deleted by hand, and are left out as deleted. Tools submitted that month that were later deleted or blocked. They are not in the other counts. Removals can happen any time later, so past months can go down slightly.

Do category shares add up to 100%?

Each count is the number of listed tools submitted that month that have the category. A tool can have several categories and some have none, so shares do not add up to 100%. Shares are of all tools submitted that month. Every month has the same category list.

How were AI Agents, MCP and AI Coding back-filled? Can history change?

Each new category was added to older tools once, on the day the category was created. For AI Coding (2026-10-01), the run looked for AI coding assistants, coding agents and AI code review in the name and slogan, and the result was checked by hand. How the 2026-09-27 run matched tools was not recorded. Tools submitted later get categories from the submit form's classifier, which the maker can change. Old tools are not re-classified when the classifier changes. 'Other' (not a developer tool) was not back-filled, so it is 0 before 2026-09. Counts are recomputed every day from live data, not frozen. A past month changes when a tool from it is later removed, or when its maker edits pricing, GitHub link or categories. A change to the submit-form classifier only affects new submissions. A new back-fill would change history: it would be listed in 'changes' with its date.

Is the current month partial?

The current month is included with "complete": false and counts up to "generatedAt". Pass ?complete=true to get complete months only.

What does "free" mean?

free / subscription / oneTime: the pricing model the maker picked for the tool (not whether they paid DevHunt). paid = subscription + oneTime. Makers can edit it.

Which tools are "not a dev tool"?

Listed tools that moderation marked "not a developer tool". They are listed but launch in their own queue. Moderation started on 2026-09-27, so this is 0 before that month: older non-developer tools were not re-checked.

All other categories existed before 2024, so makers or the classifier picked them when the tool was submitted.

1. 2024-03-05pricingOptional paid "skip the queue" launch added. Free launches keep waiting in a queue.
2. 2024-11-05pricingPaywall: new tools are asked to pay ($297 "skip the queue") before launching. Unpaid tools stay drafts. Submissions drop.
3. 2024-12-10pricingSkip-the-queue price cut from $297 to $46.
4. 2025-02-02launch-queueFree launches return: 15 free slots a week, a $49 paid launch picks any week.
5. 2026-09-27submit-flowNew submit flow: paste your website URL and the form fills itself. Submissions per day go from about 10 to 50-120. Read the jump from 2026-09 on as a change to the submit form, not a change in demand.
6. 2026-09-27moderationAutomatic moderation of submissions starts: scams are blocked, non-developer tools are marked "not a dev tool".
7. 2026-09-27categories16 new categories (including AI Agents and MCP), back-filled onto older tools.
8. 2026-09-27pricingPaid launches move to Stripe Checkout.
9. 2026-09-28launch-queueTest: new tools are offered paid launch weeks only. Tools already in the free queue keep their date.
10. 2026-09-29launch-queueTools marked "not a dev tool" get their own launch queue (10 a week) and do not compete.
11. 2026-10-01pricingTwo paid launches: $49 boosted and $19 basic. Regional prices ($29 / $9) outside high-income countries.
12. 2026-10-01categoriesAI Coding category added and back-filled.
13. 2026-10-22pricingBoost upgrades for launched tools and 3 "super boost" spots a week. Stricter check for regional prices.
14. 2026-10-31pricing$19 basic launch at the same price everywhere. No regional price for super boosts.
15. 2026-11-02pricingTest: the $19 basic launch is hidden, only the $49 launch is on sale.
16. 2026-11-05pricingTest: regional prices off. The $19 basic launch comes back as an exit offer.

• Recomputed every day. Responses are cached for up to a day, so fetching more often than hourly gets you the same numbers.
• No key and no sign-up. No hard rate limit for normal use: responses come from the cache. Please keep it to a few requests an hour.
• URLs and field names under /v1 stay stable. New fields may be added. A breaking change would go to /v2, and/v1 would keep working.
• CORS is open, so you can fetch it from a browser.