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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-03.
Written by API Evangelist on 2026-07-03 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/scrive-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.