Skip to main content

Rate Limits

Filedgr expects integrations to call the API at a bounded, predictable rate. Throttling is applied at the platform edge, and limits may be adjusted or applied per key as traffic patterns change, so build your client to degrade gracefully rather than against a specific number.

Building a well-behaved client​

  • Bound your concurrency. Avoid unbounded parallel fan-out; use a worker pool with a fixed ceiling.
  • Back off on retries. Use exponential backoff with jitter. Never retry in a tight loop.
  • Treat 429 and 5xx as retryable. Honour Retry-After when it is present on the response.
  • Prefer batch endpoints over looping single-item calls where one is available.
  • Cache what is stable. Templates and vault metadata rarely change between reads.

Note that a 403 is not retryable — it means the credentials were rejected. See Authentication.

Higher throughput​

If your integration needs sustained throughput beyond normal usage — a bulk import, a migration, or a high-volume notarization pipeline — contact Filedgr in advance with your expected request volume and shape so it can be planned for.