Our Appian application serves multiple geo regions (NA, EU, APAC). Each region uses a separate DocuSign account —and DocuSign’s REST endpoints require the accountId in the path (e.g., …/accounts/{accountId}/envelopes ). We also need to route to the correct base URI for each account/region. Goal: Make the integration scalable and configurable by: Using an HTTP Connected System so we can manage auth/base URL centrally and pass accountId as a rule input in each Integration. Dynamically selecting the correct base URI (per account/region) via DocuSign’s /oauth/userinfo (then cache it) or from the Apps & Keys page. \ Planning a future switch to JWT Grant so the integration runs with a service account (no interactive login), impersonating a user with consent. Is it possible to implement the solution. If yes what are the limitation?

Appian + DocuSign: Multi‑region setup using HTTP CS with dynamic accountId

devanshum749680 1 hour ago

Our Appian application serves multiple geo regions (NA, EU, APAC). Each region uses a separate DocuSign account—and DocuSign’s REST endpoints require the accountId in the path (e.g., …/accounts/{accountId}/envelopes). We also need to route to the correct base URI for each account/region.

Goal: Make the integration scalable and configurable by:

Using an HTTP Connected System so we can manage auth/base URL centrally and pass accountId as a rule input in each Integration.
Dynamically selecting the correct base URI (per account/region) via DocuSign’s /oauth/userinfo (then cache it) or from the Apps & Keys page. \
Planning a future switch to JWT Grant so the integration runs with a service account (no interactive login), impersonating a user with consent.

Is it possible to implement the solution. If yes what are the limitation?

Discussion posts and replies are publicly visible