Scrive · Rate Limits

Scrive Rate Limits

The Scrive Document API applies rate limiting at the User Group level. As documented, a User Group is limited to 20,000 API calls per hour, and multiple API clients within the same user group share that single limit. Scrive states that rate limits are subject to change at any time without notice. Document status callbacks (webhooks) that fail (non-2xx response) are retried at increasing intervals starting after 5 minutes, ceasing after 10 failed attempts.

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

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

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

Tagged areas include E-Signature, e-ID, Rate Limiting, and Quotas.

2 Limits Throttle: 429
E-Signaturee-IDRate LimitingQuotas

Limits

User Group API Calls user-group
requests
20000 per hour
Shared across all API clients within the same user group. Subject to change without notice.
Callback Retry document
retries
10 attempts
Failed status callbacks (non-2xx) are retried at increasing intervals starting after 5 minutes, up to 10 attempts.

Policies

Shared Group Limit
The per-hour call limit is enforced per user group, not per API client; multiple integrations under one group draw down the same budget.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 responses, as limits may change at any time.
Callback Reliability
Callback endpoints must return a 2xx quickly; Scrive retries failed deliveries with increasing intervals and stops after 10 attempts, so consumers should also reconcile state via the documents list/get endpoints.

Sources