Publishing and Go-Live
To use your Workflow Builder API integration app in production, you will need to:
- Publish any Workflow Builder workflows that the app invokes.
- Ensure that any Extension apps used in your Workflow Builder workflow steps are published.
- Promote your application’s integration key from your developer account to a production Docusign account by passing a Go-Live review, similar to the Go-Live process for the eSignature REST API.
Publishing workflows
Publishing a workflow makes it available for other users in your account to view and run, as well as making it usable by your apps in the production environment.
Before you can publish a workflow, it must first pass a short automated review, which ensures that it is configured correctly and that users have given appropriate consent for the workflow to run. You can start this review manually through the UI (see Review and Publish a Workflow).
If the prepublication check fails due to consent errors, open the URL provided in the consentUrl field and have the user provide consent, then make the API call again.
If the prepublication check passes, you can publish the workflow by calling the endpoint again and removing the isPreRunCheck=true parameter.
Go-Live
Before you can begin the Go-Live process with an API integration that uses Workflow Builder API, you must have access to the Workflow Builder API for your account.
When you are ready to start Go-Live review for your application, follow the steps described on the Go-Live overview page for the Docusign eSignature REST API.
Note: If your application fails Go-Live review, you may be required to bring it into compliance with the Rules and resource limits before you can Go-Live.
After the form is processed, your integration key will be copied into production, enabling your app to call the production API endpoints.
API endpoints
The developer and production endpoints for most Docusign APIs use slightly different paths. This table lists the endpoint base paths for each Docusign API and environment so you know how to modify your code when you migrate from the developer environment to production.
Note: To access production API endpoints, you will need to enable your integration key in the production environment. See Go-Live for more information.
Next steps
- For a list of issues that can prevent an app from passing a Go-Live review, see Go-Live troubleshooting.
- For a list of configuration changes required for the production environment, see After Go-Live.