Skip to main content
Question

Webform listInstances does not show all instances

  • July 17, 2026
  • 2 replies
  • 30 views

Forum|alt.badge.img+1

When I call a get request to listInstances,
I receive 11 instances for my webform.

But when I go to data report for my webform, there are actually 21 instances, but I am not getting all of them via API.
Anyone encountered this issue? Is there something I am missing?

 

2 replies

Forum|alt.badge.img+5
  • Docusign Employee
  • July 19, 2026

Hello ​@yarayun,

For Docusign Web Forms, Instances:listInstances is supposed to return all instances for a given web form configuration, with metadata like status and submittedDateTime, for the account and form ID you pass in. 
So getting 11 from the API while the Web Forms data report shows 21 is not expected behavior if everything is aligned.

Here are the main things to double-check:

Same account and environment

Make sure the accountId and formId in your call:
GET /api/webforms/v1.1/accounts/{accountId}/forms/{formId}/instances
match the account and specific web form you’re running the data report for (e.g., no mix of demo vs prod, or an older cloned configuration). 
No unintended filters (client_user_id)

The only documented query parameter is client_user_id, which filters the results to instances created for a specific user. 
If your GET looks like:
/instances?client_user_id=XYZ
you’ll only see instances for that user, while the Web Forms data report (if unfiltered) shows all users’ instances.
Try calling listInstances without client_user_id and compare the count again.

Statuses included

listInstances returns instances with their status (e.g., SUBMITTED) and submittedDateTime. 
Confirm whether your data report is including drafts, expired, or test instances that you might be excluding in your own logic when you count the API results.
Confirm you’re parsing the response fully

Ensure you’re not accidentally truncating the JSON array in your code (e.g., reading only the first page or first N items from the response object). The API docs don’t describe any pagination parameters for this endpoint, so everything for that form configuration should be in one response. 
If, after checking all of the above, you still see 11 vs 21 and can confirm:

same accountId and formId,
no client_user_id filter,
and you’re counting every element in the response array,
then this likely needs a deeper back-end investigation. In that case, I’d recommend opening a Docusign Support case.


 

Thanks and regards,

Mahmoud.

 

 


Forum|alt.badge.img+1
  • Author
  • Newcomer
  • July 20, 2026

Yes, it is the same accountId and formId.
I have not applied any filter parameter. My endpoint is just /instances
No pagination.
I have contacted Docusign Support about this.

You clearly also used AI to generate a generic response.

Thanks.