Skip to content

Commit

Permalink
Merge pull request #571 from hirosystems/chore/rate-limits
Browse files Browse the repository at this point in the history
chore: clarify rate-limits for API traffic are not per IP.
  • Loading branch information
diwakergupta authored Dec 1, 2023
2 parents c7aca08 + ea4d572 commit e8c84db
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/rate-limiting.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,14 @@ title: Rate Limiting

## Rate Limiting for Hiro APIs

Hiro’s Rate Limit per Minute (RPM) is applied to all Hiro-hosted API services. As of November 9th, 2023, our policy is:
The following rate-limits (in requests per minute, or RPM) are applicable for all Hiro APIs as of [November, 2023](https://www.hiro.so/blog/updated-rate-limits-for-hiro-apis):

- 50 RPM per client IP for unauthenticated traffic (without an API key)
- 500 RPM per client IP with an authenticated API key
- 50 requests per minute, per client IP, for unauthenticated traffic (without an API key)
- 500 requests per minute (regardless of origin IP) with an authenticated API key

These new rate limits help us ensure fair usage of Hiro APIs and provide the best possible service as our community of developers and applications grow and scale.

If you’re interested in the higher 500 RPM limit, please [complete this form](https://survey.hiro.so/hiroapi) to apply for an API key.
Please [complete this form](https://survey.hiro.so/hiroapi) to apply for an API key.

### STX Faucet Rate Limit

Expand Down

1 comment on commit e8c84db

@vercel
Copy link

@vercel vercel bot commented on e8c84db Dec 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please sign in to comment.