Skip to main content

I'm working on a DocuSign integration using the eSignature API (sandbox environment) and I need to configure BCC email settings on envelopes using the email_settings.bccEmailAddresses field.

The request works perfectly in the API Explorer:
https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeemailsettings/create/?explorer=true
 

However, when I try the same request from my Ruby application (using the official SDK), I get this error only when bccEmailAddresses is included:
 

{
  "errorCode": "API_REQUEST_IS_FORBIDDEN",
  "message": "The API request is forbidden. Request blocked due to excess usage"
}
HTTP status: 444
 

Without the email_settings, the envelope is created successfully.
I also tried to set email_settings during the create_envelope call, but it did not work — the field is either ignored or causes the same error depending on how it's passed. Even when correctly structured (and working in the API Explorer), it fails in the application context.

Details:

  • SDK: docusign_esign 5.2.0

  • The authenticated user is an admin and has canManageAccount permission

  • OAuth2 is via JWT impersonation

  • Envelope status is "created"

  • Endpoint used: 
    POST /v2.1/accounts/{account_id}/envelopes
    POST /v2.1/accounts/{account_id}/envelopes/{envelope_id}/email_settings

    After some research, I suspect that BCC Email Archive is not enabled for my sandbox account, which may be the root cause of the 444 error.


Could someone confirm whether this feature needs to be manually enabled in sandbox?

Hello Luciene,

 

This is Alice, Developer Support Engineer at Docusign. It is nice to meet you.

 

You are correct, the Docusign API Explorer frontend follows a different set of rules for commodity but should not be used as an actual custom API integration reference.

Indeed, your investigation pointed into this direction, the bccEmailAddresses API is disabled as our platform's default and is not limited for sandbox environments.

 

With that said, if such is key for your new integration, please follow up with me and my team here and we will be working in more details with you: https://support.docusign.com/s/cases

 

Best regards,

 

Alice Goglione (she/her) | Developer Support Engineer II

NPikcCCy65KbqEI-Qwh7_-2s-pMm9JQ0NWFuBi_87cbSqVm1ezaRscPxxxn8hNpSDIntAJY_Df2XcFQnyrz2xpyCN7Almg7rZJJa3P3UjP7pKPmIUPLHMjSgigZnQcgQfxtGOcR1EW4EQ-9RuoTfLA


Reply