Limits and defaults.

00How to read the tables

01API keys and request rates

A key is counted in fixed windows: one clock second and one clock minute. Either window can refuse a request, and the message names which one.

Over the limit, REST routes answer with a 429 and a Retry-After header in seconds. The public GraphQL API answers with the same status and the code RATE_LIMITED.

HTTP/1.1 429 Too Many Requests
Retry-After: 1

{
  "statusCode": 429,
  "message": "Rate limit exceeded (second window)",
  "retryAfterSeconds": 1
}

HTTP/1.1 429 Too Many Requests
Retry-After: 1

{ "errors": [ {
  "message": "Rate limit exceeded (second window)",
  "extensions": { "code": "RATE_LIMITED" }
} ] }

Wait for the Retry-After value, then retry with the same idempotency key. See API keys for integrators and Event ingestion.

02Product events

These apply to usage events sent to /api/v1/product-events, from your servers or, with a token, from a browser. See Send product events for the request shape.

03Usage and event ingestion

04Outbound webhooks

Settings, Webhooks sends lead.created, lead.updated and lead.deleted to your web addresses. A webhook.test event is sent only by Send test event.

05Forms

06Files and attachments

07Email tracking

08Support

09Revvly Assistant

10Tasks and list sizes

11Sessions and tokens

12Workspace defaults

Where a setting has a screen, it is on Settings, General unless noted.

13Scheduled windows

Daily jobs run on the platform clock. They are not workspace settings.