Not able to send instant reminder email to pending recipients through DocuSign API

[pradeepkmr88]

Hi, could you please advise here. I want to send instant reminder email to pending recipients using below request. but I am getting 400 error "bad request".

Method:PUT, RequestUri: 'https://demo.docusign.net/restapi/v2/accounts/{AccountId}/envelopes/{envelopeId}?resend_envelope=true', Version: 1.1, Content: , Headers: { Accept: application/json X-DocuSign-Authentication: {"Username":"xx", "Password":"xx", "IntegratorKey":"xx"} }

[InbarGazit]

The code above uses legacy authentication, you need to use OAuth 2.0 with an access token and do NOT use X-DocuSign-Authentication

[pradeepkmr88]

Hi Inbar,

Thanks for your response !.

I tried with OAuth 2.0 access with below code. But still, I am not able to send instant reminder email.

If I am setting reminderDelay = "1", reminderFrequency = "1" then it is sending reminder email after 24hr. But we need to send reminder email on user request.

string apiUrl = $"https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes/{envelopId}? resend_envelope=true"; using (HttpClient client = new HttpClient()) { client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", accessToken); string reminderApiUrl = $"{apiUrl}"; var reminderRequest = new { reminderEnabled = "true", reminderDelay = "0", reminderFrequency = "0" }; string reminderJson = Newtonsoft.Json.JsonConvert.SerializeObject(reminderRequest); StringContent reminderContent = new StringContent(reminderJson, Encoding.UTF8, "application/json"); HttpResponseMessage reminderResponse = await client.PutAsync(reminderApiUrl, reminderContent);

Is there POST API for send reminder email? I found this one post API but it's not working. ([https://demo.docusign.net/restapi/v2/accounts/{{accountId}}/envelopes/{{EnvelopeId}}/reminders])

Please suggest on this. Thanks

[garg-mudit]

Hi @pradeepkmr88 , Is this issue still valid ? Please let us if we can help you out regarding the same.

Thank You.

CC: @InbarGazit

[bhavya-c]

Hi @pradeepkmr88 , As we haven’t received any updates on this issue, we’re closing it for now. Please feel free to reopen the issue if the problem persists or if you have additional information to share.