ZapSign API
English
English
  • General Information
  • Getting Started
  • ZapSign Environments
  • Ready-to-use requests!
  • Authentication
    • Static token
    • JWT Authentication
      • Get access token
      • Refresh your access token
  • Types of Tokens
  • API versioning
  • Rate Limit Policies
  • Incident alerts
  • How Payment Works
  • Status Code
  • Account
    • Plan Information
    • List account users
    • Create account users
    • Delete account user
  • Documents
    • Create document via Upload
    • OneClick (ClickWrap)
      • Create document (OneClick)
    • Create document via Template
    • Add attachment (extra document)
    • Add attachment (extra document) via Template
    • Detail document
    • List documents
    • Delete document
    • Document Audit Trail
    • Optional: Place signatures
    • Reject Documents
  • Signature Validation
  • Signers
    • Detail signer
    • Update signer
    • Add signer
    • Delete signer
    • Batch sign via API
    • Reject Documents by User
  • Templates
    • Create template (DOCX)
      • Configure Template Form
    • List templates
    • Get template
    • Update template
    • Delete template
  • Partnerships
    • Update Payment Status
    • Create Account
  • TIMESTAMP
    • Add timestamp
  • Background Check
  • Introduction
  • Understanding the Result
  • Creating a Background Check
    • Person Check
    • Company check
  • Retrieve a Check
  • Check details
  • Webhooks
    • How webhooks works
    • Testing webhooks on ZapSign
    • Create Webhook
    • Webhooks logs
    • Events
      • Document
        • Doc created
        • Doc deleted
        • Created signer
      • Signer
        • Signature request send
        • Document viewed
        • Reading confirmation
        • Doc signed
        • Doc refused
        • Email bounce
        • Failed Validation
      • Background check
        • Background check completed
    • Reprocessing Documents and Webhooks
    • Delete Webhook
  • Widget
    • How widget works
Powered by GitBook
On this page

Was this helpful?

Rate Limit Policies

To provide a more stable and efficient user experience, we have implemented rate limit policies to ensure the best possible performance of our API for all users.

PreviousAPI versioningNextIncident alerts

Last updated 9 months ago

Was this helpful?

Overall Limit and Application For all public endpoints of the application, the rate limit is set to 500 requests per minute. This limit is applied per IP address or valid authentication token, ensuring that each entity (IP or token) has a fair usage quota.

Rate Limit Operation

  • Request Limit: Each valid IP or authentication token is allowed up to 500 requests per minute to the public endpoints of the application.

  • Time Windows: The request count is tracked in 1-minute time windows, resetting every new minute.

  • Rate Limit Feedback: When the 500 requests per minute limit is reached by a specific IP or token, subsequent requests within the same 1-minute period will receive a response with HTTP status code 429 (Too Many Requests).

BEST PRACTICES FOR DEVELOPERS

To avoid hitting the request limit, we recommend following these best practices:

Support and Contact If you encounter issues related to rate limits or need a custom limit for specific needs, please contact our support team at support@zapsign.com.br or WhatsApp +55 11 4040-1991.

For more details, please visit the .

original documentation
Cover

Implement Caching: Use caching techniques to reduce the number of repeated requests to the server.

Cover

Request Optimization: Aggregate multiple operations into a single request when possible.

Cover

Error Management: Implement exponential backoff logic to handle rate limit exceeded responses (HTTP 429).