Skip to main content
arrow-left Back to Docusign.com
Solved

User Management API - User List Failed Call

  • December 23, 2024
  • 5 replies
  • 50 views
N
New Voice
Forum|alt.badge.img+2

Hello,

 

We were getting ready to “Go-Live” with our first DocuSign integration but when we went to start the process, it is showing that we don’t have 20 consecutive Api calls. Upon closer review, it looks like the “GetUsers” endpoint (list | REST API | Docusign) is registering as Failed when it cannot find a user. This doesn’t make sense because it is still a successful call is it not?

 

We are using this to check and see if the user exists before creating the signature request. If they do not exist then we call the user Add API.

 

 

Any insights into this? Is there a better approach that I am missing? Or do we just need to get past this initial fail and run multiple more tests to get to 20 consecutive successful calls?

Best answer by JohnSantos

​@Nicholas H. 

First, a bit of context about DocuSign’s Go-Live process: DocuSign requires 20 consecutive successful API calls in the Demo environment before approving an integration for Production. A 400 from the GET call is generally not considered a successful call. That’s why you’re hitting a snag—DocuSign flags the 404 “User not found” response as a failed call, preventing you from racking up the 20 consecutive successful calls.

Skip the user existence check (if possible). One approach is to simply create the user without checking if they exist.

This avoids the 400 entirely, so all calls remain “successful” as far as DocuSign’s consecutive-call requirement is concerned.

View Original
Is this content helpful?

5 replies

JohnSantos
Valued Contributor
Forum|alt.badge.img+18
  • JohnSantosValued Contributor
  • Valued Contributor
  • 968 replies
  • Answer
  • December 23, 2024

​@Nicholas H. 

First, a bit of context about DocuSign’s Go-Live process: DocuSign requires 20 consecutive successful API calls in the Demo environment before approving an integration for Production. A 400 from the GET call is generally not considered a successful call. That’s why you’re hitting a snag—DocuSign flags the 404 “User not found” response as a failed call, preventing you from racking up the 20 consecutive successful calls.

Skip the user existence check (if possible). One approach is to simply create the user without checking if they exist.

This avoids the 400 entirely, so all calls remain “successful” as far as DocuSign’s consecutive-call requirement is concerned.

Welcome to the DocuSign Community! Your feedback is highly valued. If you find my response helpful, please give it a "Like" and consider marking it as the "Best Answer" to assist others with similar issues.
N
1 person likes this
  • N
    Nicholas H.
N
New Voice
Forum|alt.badge.img+2
  • Nicholas H.New Voice
  • Author
  • New Voice
  • 9 replies
  • December 24, 2024

​@JohnSantos 

 

Okay I will give that a try and just call the create user regardless. If this is the case, then I would assume that the create user will not throw an error if the user already exists and will just return the user info of the pre-existing user?

N
New Voice
Forum|alt.badge.img+2
  • Nicholas H.New Voice
  • Author
  • New Voice
  • 9 replies
  • December 24, 2024

I made the change and gave it a try and it did work by just calling the CreateUser… it did not add a duplicate account or throw an error. It returned the existing account info which works out. Thank you ​@JohnSantos 

J
Newcomer
Forum|alt.badge.img
  • JENANI1Newcomer
  • Newcomer
  • 2 replies
  • March 7, 2025

Need user List from Condor

J
Newcomer
Forum|alt.badge.img
  • JENANI1Newcomer
  • Newcomer
  • 2 replies
  • March 7, 2025

Need User List from Docusign

Reply


Most helpful members this week

Code of Conduct

Docusign Community

Code of Conduct