Skip to main content
Configure and connect the DocuSign Connector to Grand Central.

​
Prerequisites

Before you begin, confirm the following:
  • You have completed the steps in Get started.
  • You have an active contract with DocuSign and your own accounts and credentials set for DocuSign services.

​
Configuration

To configure your connector, follow these steps:
  1. Set your API Management (APIM) subscription key in the header as follows:
    • Key: api-key
    • Value: YOUR_SUBSCRIPTION_KEY
  2. Ask the Grand Central team to set up a connection with DocuSign, and provide the following details for JSON Web Token (JWT) generation:
    • docusign-client-id
    • docusign-user-id
    • docusign-account-base-url
    • docusign-cert-thumbprint
  3. Configure the DocuSign baseURL in the gc-applications-live repository in the connector’s values.yaml file: 
    # DocuSign environment base URL
docusign.base.url=BASE_URL
# DocuSign account ID
docusign.account.id=ACCOUNT_ID
  4. Verify the connector’s values.yaml file location in the repository: 
    ├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            └── gc-docusign
                └── correspondence-v0.values.yaml
  5. Register your environment callback URL ({CORRESPONDENCE_INBOUND_BASE_URL}/webhooks/documents-signature) in DocuSign Connect.
  6. Configure how Grand Central receives asynchronous updates from DocuSign for real-time signing status processing in the correspondence-inbound-v0.values.yaml file. The following table lists the ASB configuration properties:
PropertyDescriptionExample value
asb.event.versionVersion of the Async Service Bridge (ASB) schema.1.0.0
asb.event.typeThe ASB event type for outgoing messages.com.backbase.correspondence.event.spec.v1.DocumentSignatureEvent
asb.event.sourceThe ASB source for outgoing messages.com.backbase.correspondence
asb.event.topicThe ASB topic for outgoing messages.document-signature
asb.producer.apiUriThe callback URI for receiving incoming events.http://asb-producer-v0.synchub-producer.svc.cluster.local

​
Test your integration

To access the Correspondence Unified API, include your Grand Central subscription key in the request header. If you don’t have a key, contact the Grand Central team to have one provisioned. The following table lists the header you must include on each request.
KeyValue
api-keyYOUR_SUBSCRIPTION_KEY
For sample requests, import the Postman collection from the Grand Central documentation repository.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Grand Central gateway can’t establish a handshake with the DocuSign endpoint. This typically indicates an upstream service outage at DocuSign or a network routing failure.Solution: Verify the operational status of the DocuSign environment with DocuSign. If the service is operational, contact the Grand Central team.
Cause: The request to DocuSign exceeded the configured timeout threshold. This can occur during high load or network latency issues.Solution: Verify the operational status of the DocuSign environment with DocuSign. If the service is operational, contact the Grand Central team to review timeout configurations.
Cause: The credentials provided during setup are incorrect.Solution: Verify your credentials with DocuSign and contact the Grand Central team to update the connection.
Cause: The number of incoming requests exceeded the defined threshold for your subscription tier. This response protects the stability of the Grand Central and partner infrastructure.Solution: Review your application’s request patterns to identify unexpected spikes. If you require higher throughput, contact the Grand Central team to request an adjustment to your APIM rate limit policy.

​
Need more help?

Contact support

Reach out to the Grand Central team for assistance with environment setup or rate limit increases.