Folk · Rate Limits

Folk App Rate Limits

The Folk External API applies rate limiting per API key. Every response carries the standard rate-limit headers X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (UTC epoch seconds), and a 429 Too Many Requests response includes a Retry-After header telling the client how many seconds to wait. Folk's published schema illustrates the window with an example limit of 1000 requests, but it does not commit to a fixed numeric ceiling in the reference, so clients should read the headers at runtime rather than hard-coding a value. List endpoints are cursor-paginated (limit + cursor) to keep result sets bounded.

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

It captures 2 rate-limit definitions, measuring requests and items.

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

Tagged areas include CRM, Relationships, Contacts, Rate Limiting, and Quotas.

2 Limits Throttle: 429
CRMRelationshipsContactsRate LimitingQuotas

Limits

Requests Per API Key apiKey
requests
header-advertised (example 1000 per window)
Actual ceiling is advertised at runtime via X-RateLimit-Limit; the 1000 figure is an illustrative example in the published schema.
List Page Size request
items
100 max (default 20)
Controlled by the limit query parameter on list endpoints.

Policies

Cursor Pagination
List endpoints return a nextCursor and accept limit + cursor parameters to bound response size and paginate large collections.
Backoff Strategy
On a 429 response, honor the Retry-After header and apply exponential backoff with jitter before retrying.
Header-Driven Throttling
Clients should read X-RateLimit-Remaining / X-RateLimit-Reset on every response and self-throttle rather than assume a fixed limit.

Sources