Quick answer
Clerk documents invitation creation as 100/hour individual; 25/hour bulk. Organization invitations use separate documented counts.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| invitation creationOrganization invitations use separate documented counts. | 100/hour individual; 25/hour bulk | Instance | ClerkAug 22, 2026 |
Why does this limit matter?
A migration script using the bulk endpoint can throttle at a lower operation count than individual calls.
This value is scoped to Instance; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Separate user and organization invitations and individual versus bulk operations.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Retries without idempotency can create duplicate invitations.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related