Skip to main content

I am implementing a integration with my browser application and Docusign. For this I have to call the endpoint from the browser and for this I am using the default fetch command from node. This command results in a unstoppable options command which includes a unstoppable Request-Id header. I have tried using a client instead of the browser which results in everything working perfectly. I have implemented the authentication but this is the final hurdle.

Officially Request-Id is not specified in the HTTP schema but a lot of browsers do send this when cross origin querying endpoints. What do you suggest I change or is there a chance the Docusign api will support this?

For completeness the error in the console: Access to fetch at 'https://demo.docusign.net/restapi/v2.1/accounts/${accountId}/envelopes/' from origin 'http://localhost:8080' has been blocked by CORS policy: Request header field request-id is not allowed by Access-Control-Allow-Headers in preflight response.

The headers are coming from ApplicationInsights, I can disable them but they help our team debug more easily.

Besides Request-Id also traceparent would be beneficial in adding as allowed headers.


There is no custom configuration at the moment to allow any non-default headers.

You will need to remove these from your requests to work.

You can raise this as an idea here: https://community.docusign.com/ideas