API template library

Simulate the DocuSign Connected Fields API

A WireMock simulation of DocuSign's REST API — covering the tab groups that installed extension apps can verify, with their data-verification contracts, connected-object types and validation rules.

Vendor
DocuSign
Functionality
Verifiable tab groups by extension app
Spec version
1.0.0
Endpoints
1
Stubs
7
Protocol
REST
Validation
AI-validated Before publication, an AI agent exercised these endpoints against the real DocuSign API through WireMock's recording proxy, and the recorded traffic was used to verify each stub's request and response shapes.

Live sandbox · no signup, no API key

DocuSign Connected Fields API

A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.

Base URL
https://ygyl7g.wiremockapi.cloud

GET List the account's verifiable tab groups

curl -s -X GET 'https://ygyl7g.wiremockapi.cloud/v1/accounts/2f5a7c9e-1b3d-4f6a-8c2e-4a6b8d0f2a41/connected-fields/tab-groups' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

GET Only the Email Verification app

curl -s -X GET 'https://ygyl7g.wiremockapi.cloud/v1/accounts/2f5a7c9e-1b3d-4f6a-8c2e-4a6b8d0f2a41/connected-fields/tab-groups?appId=b41c7e90-2d5f-4a8e-8b6c-3f9d1e7a2c58' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'
Method Path Summary
GET /v1/accounts/{accountId}/connected-fields/tab-groups Returns all tabs associated with the given account

Unauthenticated WireMock Cloud demo sandbox for DocuSign — not an official DocuSign sandbox, and it returns simulated example data only.

What's inside the Connected Fields template

Connected Fields has one operation, and it answers a narrow question: which envelope tabs can this account's extension apps verify against an outside system of record? For Lucky Shrub Sales the answer is three apps. A bank account check exposes account number, holder name and a nine-digit routing number; an email check exposes a single address; and a custom Lucky Shrub Customer Records app exposes phone verification plus a customer id in the form LS-000000 and a Gold, Silver or Bronze loyalty radio group. Each tab carries the validationPattern a sender UI should enforce, and the custom app's tabs add the connected-object namespace, type name and verify URI.

  • Data verification apps — bank account ownership and email verification, each with its action contract and connection instances
  • Connected-object app — custom VerifyPhoneNumberInput and VerifyCustomerInput types with connectedFieldsData on every tab
  • Tab definitions — text and radio tabs with validation patterns, messages and required-for-extension flags
  • App filtering — the optional appId query parameter, narrowing the response to a single app

DocuSign Connected Fields mock API FAQ

No. The Email Verification app's id matches in upper case as well as lower, and the response returns the canonical lower-case id. An appId that matches no installed app returns an empty array rather than an error.

An empty array. Only Lucky Shrub Sales has apps installed, so the Lucky Shrub Legal account id, or any other well-formed GUID, gets []. A value that isn't a GUID at all is rejected with 400 INVALID_REQUEST_PARAMETER, naming the bad id.

No, and the real API can't either: apps are installed from the DocuSign App Center, and this endpoint only reports them. The three apps are fixed, which makes the response a stable fixture for code that renders tabs or builds envelopes from them. A different mix of apps is a one-file change once the template is copied into WireMock Cloud.

Any Bearer string is accepted. Leaving the Authorization header off returns 401 AUTHORIZATION_INVALID_TOKEN, which is handy for testing the re-authentication path. Don't send a real DocuSign access token to this public sandbox.

Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.