Kinde · Rate Limits

Kinde So Rate Limits

Kinde applies both a rate limiter and a concurrency limiter to the Management API but does not publish fixed numeric per-minute request thresholds - the basic rate limiter restricts requests per minute and Kinde may rate limit incoming traffic, adjusting limits per account on request. Two hard, documented limits do apply to every account: a maximum page size of 500 on GET endpoints that accept the page_size parameter, and a maximum of 100 objects updated in a single request to bulk POST/PATCH endpoints. When throttled the API returns HTTP 429, and the RateLimit-Reset response header returns the number of seconds until the limit resets.

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

It captures 4 rate-limit definitions, measuring requests, concurrent requests, records, and objects.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Authentication, User Management, Identity, Rate Limiting, and Quotas.

4 Limits Throttle: 429
AuthenticationUser ManagementIdentityRate LimitingQuotas

Limits

Management API Request Rate account
requests
not published (per-minute limiter; adjustable per account)
Basic rate limiter restricts requests per minute; Kinde does not publish a fixed number.
Concurrency account
concurrent requests
not published
A concurrency limiter caps simultaneous in-flight requests in addition to the rate limiter.
Page Size request
records
500
Maximum page_size on GET endpoints that support pagination.
Bulk Update Objects request
objects
100
Maximum objects updatable in a single POST/PATCH request to bulk endpoints.

Policies

Retry-After / RateLimit-Reset
On a 429, the RateLimit-Reset header returns the number of seconds until the rate limit resets; clients should wait that long before retrying.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor the RateLimit-Reset header.
Pagination
Use the maximum page size of 500 and follow next-page tokens rather than issuing many small requests to reduce rate-limit pressure.

Sources