Hashnode · Rate Limits

Hashnode Rate Limits

Rate limit definitions for the Hashnode GraphQL API. Hashnode fronts the gql.hashnode.com endpoint with Stellate, a GraphQL edge-cache CDN, which enforces the rate limits. Unauthenticated requests are throttled per IP address; authenticated requests (Personal Access Token in the Authorization header) are throttled per token.

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

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

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

Tagged areas include Blogging, Content, Developer Community, Rate Limiting, and GraphQL.

2 Limits Throttle: 429
BloggingContentDeveloper CommunityRate LimitingGraphQLStellate

Limits

Unauthenticated Request Limit ip
requests_per_minute · minute
2000
Applied per IP address for requests without an Authorization header via Stellate CDN
Authenticated Request Limit api-key
requests_per_minute · minute
500
Applied per Personal Access Token for requests with an Authorization header via Stellate CDN

Policies

Stellate Edge Caching
Hashnode uses Stellate as a GraphQL CDN in front of gql.hashnode.com. Cacheable read queries may be served from the edge cache and may not count against per-request rate limits.
Backoff Strategy
Clients receiving a 429 response should implement exponential backoff with jitter, honoring the Retry-After header when present.
Authentication Preferred
Authenticated requests with a Personal Access Token have a higher per-minute cap (500 rpm) than unauthenticated requests (2000 rpm per IP). Use authentication for production integrations to avoid shared IP throttling.
Personal Access Token Generation
Personal Access Tokens are generated at https://hashnode.com/settings/developer. Tokens must be passed in the Authorization header of each GraphQL request.
Fair Use
Sustained high-volume usage that materially impacts shared infrastructure may be subject to additional throttling or account review regardless of documented limits.