PropelAuth · Rate Limits

Propelauth Rate Limits

Rate-limit posture for the PropelAuth backend APIs and end-user API key validation surface. PropelAuth does not publish explicit per-tenant request-per-second limits for the backend Integration API; production limits are tuned per customer. The end-user API key product enforces customer-configured per-key rate limits (with a 5,000,000-validation Advanced API Keys add-on) returned in the validation response payload.

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

It captures 4 rate-limit definitions.

The profile also includes response codes documented for throttled and quotaExceeded.

Tagged areas include Authentication, Rate Limiting, API Keys, and B2B.

4 Limits Throttle: 429 Quota: 429
AuthenticationRate LimitingAPI KeysB2B

Limits

per-project
Production rate limits are tuned per customer; staging/test instances enforce conservative limits.
per-end-user-key
Customer-configured validation cap per key; Advanced API Keys add-on raises monthly validations.
per-user
PropelAuth throttles magic-link issuance per email to prevent abuse.
per-client
OAuth 2.1 token endpoint rate limits apply per registered MCP client.

Sources