Hi when our application connects to DocuSign via the API when calling a specific endpoint, I get an unspecified error message. The endpoint our system calls is: /restapi/v2.1/accounts/{AccountID}/users. The status code returned is a status 400. The logs don't provide many details. Has anyone experienced this issue when calling this endpoint?
We are using SailPoint's IdentityNow connector to make the API call. The API call is used for account aggregation of users of DocuSign onto the SailPoint system. After 799 accounts are aggregated the status 400 error occurs. We expect the connector to pull all 1033 accounts from DocuSign onto SailPoint.
Mayooran NavamanyPosted May 15, 2024, 9:36 AM
Here are a few steps you could take to troubleshoot the problem:
Check API Documentation: Review the DocuSign API documentation for the
/restapi/v2.1/accounts/{AccountID}/usersendpoint to ensure that you're using the correct parameters and formatting for your request.Verify Authentication: Ensure that your authentication credentials (such as API key, OAuth tokens, etc.) are correctly configured and have the necessary permissions to access the endpoint.
Rate Limiting: DocuSign might have rate limiting policies in place. If you're hitting a rate limit, it could result in a 400 error. Check the documentation for any rate limits and make sure you're not exceeding them.
Request Payload: Double-check the payload you're sending with the request. Make sure it's correctly formatted and includes all required fields.
Error Handling: Implement more robust error handling in your code to capture and log any additional error details returned by the API.
Divide and Conquer: Since the error occurs after aggregating 799 accounts out of 1033, try to narrow down the issue by aggregating smaller batches of accounts. This can help identify if the problem is related to a specific subset of accounts.
Contact Support: If you've exhausted your troubleshooting options and are still unable to resolve the issue, consider reaching out to DocuSign support for assistance. Provide them with as much detail as possible about your API request and the error you're encountering.
Additionally, since you're using SailPoint's IdentityNow connector to make the API call, you may want to check if there are any known issues or limitations with the connector that could be contributing to the problem. SailPoint's support resources or community forums could be helpful in this regard.
By systematically investigating these areas, you should be able to identify the root cause of the 400 error and take appropriate action to resolve it.