Hashnode · Rate Limits

Hashnode Rate Limits

Rate limits for the Hashnode GraphQL API, taken from Hashnode's own agent-skill reference. This REPLACES a 2026-05-04 bulk sweep file that described 2,000 rpm unauthenticated / 500 rpm authenticated enforced by a Stellate GraphQL CDN in front of gql.hashnode.com. That description no longer matches anything Hashnode publishes: the endpoint it named now 301s to a deprecation notice, and Hashnode's current documentation states plainly that rate limiting is NOT currently enforced by the server. The published numbers are targets, not a contract.

Hashnode Rate Limits is the machine-readable rate-limit profile for Hashnode on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, across the all tier, measuring requests_per_minute.

Limit state is signalled in the rate_limit_headers, retry_after, and note response headers, and an exhausted limit returns HTTP not documented.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and note.

Tagged areas include Blogging, GraphQL, and Rate Limiting.

2 Limits Exhausted: HTTP not documented rate_limit_headersretry_afternote
Transcribed from the provider's documentation on 2026-08-13 — raw.githubusercontent.com/Hashnode/gql-skill/main/skills/....
View Source
BloggingGraphQLRate Limiting

Limits

Query target unspecified
requests_per_minute · minute
20000
Published target only; Hashnode states it is not enforced by the server.
Mutation target unspecified
requests_per_minute · minute
500
Published target only; Hashnode states it is not enforced by the server.

Policies

Access is gated by subscription, not by quota
Since 2026-05-13 the binding constraint on the Hashnode API is the Pro plan, not a request budget. Publication-scoped reads and all mutations return FORBIDDEN unless the target publication is on Pro.
Query caching
Query responses may be cached for up to ~25 seconds; mutations are never cached. A read immediately after a write can return stale data.
Clamping is silent
Page sizes above the cap are clamped rather than errored, so a client asking for 500 receives 100 with no signal. Never infer completeness from a short page.
Personal Access Token generation
Tokens are generated at https://hashnode.com/settings/developer and passed in the Authorization header.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/hashnode-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.