---
title: "Rate limits and request size: 1Post docs"
url: "https://get1post.com/docs/api-rate-limits.md"
canonical_url: "https://get1post.com/docs/api-rate-limits"
last_updated: "2026-10-26"
type: "reference"
summary: "How many requests a key and an address may send, how the rate_limited error tells you when to retry and the size limit on bodies."
related: ["https://get1post.com/docs/api-idempotency.md", "https://get1post.com/docs/errors.md", "https://get1post.com/docs.md"]
---

# Rate limits and request size: 1Post docs

How many requests a key and an address may send, how the rate_limited error tells you when to retry and the size limit on bodies.

Each key has a request rate limit, and public routes have a smaller one per address. Over the limit the API answers rate_limited with a Retry-After header saying how many seconds to wait. Bodies are limited to 256 KB on API routes, so media goes to storage through a signed address.

- Key routes: limited per key; the numbers are in the security scheme of the [reference](https://get1post.com/docs/api.md).
- Public routes and free tools: 30 requests a minute and 1,000 a day per address, with no key.
- Bodies: 256 KB on API routes. Larger files use [media uploads](https://get1post.com/docs/api-media-uploads.md).

Back off for the number of seconds in Retry-After, then retry with the same Idempotency-Key.

## Questions

**Is the limit per workspace or per key?**

Per key. Two keys have two separate limits.

## Related

- [Idempotency: 1Post docs](https://get1post.com/docs/api-idempotency.md)
- [1Post API error codes and how to fix each](https://get1post.com/docs/errors.md)
- [1Post docs: composer, scheduling, API, webhooks, MCP](https://get1post.com/docs.md)