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.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/scrive-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.