Skip to main content
Question

Performance Delay with Multiple ListStatusChangesAsync Calls Using Custom Fields

  • August 5, 2026
  • 1 reply
  • 12 views

Forum|alt.badge.img
  • Conversation Starter

We are using the ListStatusChangesAsync API to retrieve DocuSign envelopes for multiple account numbers. For each account number, a separate API request is sent to fetch the related envelope details, including documents and custom fields. All requests are executed in parallel, and the responses are combined into a single result set.

We have observed that the loading time increases as the number of account numbers increases. We would like to understand the following:

  • Does DocuSign apply any throttling or delays when multiple API requests are executed simultaneously?
  • Is there a recommended limit for concurrent API requests?
  • Does retrieving additional information, such as documents and custom fields, significantly affect performance?
  • Is there a more efficient approach for retrieving envelopes associated with multiple account numbers?

Any suggestions or best practices would be greatly appreciated.

1 reply

Forum|alt.badge.img+7
  • Docusign Employee
  • August 7, 2026

Hello 

  1. Throttling / delays

    • Docusign enforces rate limits, not per-request “sleep” delays.
    • You’ll see this via X-RateLimit-Limit,  headers 
  2. Concurrent requests

    •  Keep total calls within the hourly account limit and avoid tight per-envelope polling (≥20-minute intervals for status checks is recommended).
  3. Including documents/custom fields

    • Adding include=documents,custom_fields makes each ListStatusChanges call heavier  
    • As you scale accounts/envelopes, this will noticeably increase latency.
  4. More efficient approach

Thankyou

Thanks & Regards

Sai HariPriya Dandamudi | Developer Support Engineer | DocuSign

 

 

A picture containing clipartDescription automatically generated