Misskey · Rate Limits

Misskey Rate Limits

Rate limit definitions for the Misskey API surface. Misskey is open-source software where each instance administrator configures rate limiting independently. The Misskey backend exposes rate limit information via standard response headers. Job queue rate limits (delivery, inbox, relationship) are configurable in the instance .config/default.yml. Per-endpoint endpoint-level rate limits are enforced by the backend and controlled via the roles system. Default values below reflect typical instance configurations; consult your specific instance's /api-doc for authoritative limits.

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

It captures 6 rate-limit definitions, across the default, job-queue, and role-based tiers, measuring requests_per_minute and jobs_per_second.

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

Tagged areas include Open-Source, Social Networks, Fediverse, Rate Limiting, and Quotas.

6 Limits Throttle: 429 Quota: 429
Open-SourceSocial NetworksFediverseRate LimitingQuotasThrottling

Limits

Default API Rate Limit api-key
requests_per_minute · minute
60
Sign-in Rate Limit ip
requests_per_minute · minute
10
ActivityPub Delivery Job Rate server
jobs_per_second · second
128
ActivityPub Inbox Job Rate server
jobs_per_second · second
32
Relationship Job Rate server
jobs_per_second · second
64
Role-Based Rate Limit api-key
requests_per_minute · minute
-1

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter, honoring the Retry-After header when a 429 response is received.
Burst Handling
Short bursts above the steady-state limit are tolerated up to the documented burst ceiling before throttling engages. Burst windows are sliding.
IP-Based Limiting
Unauthenticated and authentication endpoints apply rate limits per source IP. Ensure your reverse proxy correctly forwards the client IP via X-Forwarded-For and that the Misskey trustProxy configuration matches your infrastructure.
Role Overrides
Instance administrators may grant roles that relax or remove rate limits for specific users or bots via the Misskey roles system.
Fair Use
Even on self-hosted or uncapped enterprise deployments, sustained usage that materially impacts shared infrastructure may be subject to fair-use throttling at the discretion of the instance administrator.