> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL. > > Documentation indexes by section: > - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt > - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt > - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt > - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt > > Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth > Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks > > OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json > MCP server: https://docusign.docs.buildwithfern.com/_mcp/server # Connected Fields API ## Docs - [Connected Fields API concepts](https://developers.docusign.com/docs/connected-fields-api/concepts.md): Learn about the basic concepts and objects used by the Connected Fields API. - [How to send an envelope with extension app data verification fields](https://developers.docusign.com/docs/connected-fields-api/send-envelope-with-data-verification-fields.md): This topic demonstrates how to set connected fields in a document and send an envelope with a data verification field. - [Authentication](https://developers.docusign.com/docs/connected-fields-api/auth.md): Learn how to authenticate to call the Connected Field API endpoint. - [Go-Live and API base paths](https://developers.docusign.com/docs/connected-fields-api/go-live.md): Learn how to promote a Connected Fields API integration from the developer environment to production. - [API Categories](https://developers.docusign.com/docs/connected-fields-api/reference.md) - [ConnectedFields](https://developers.docusign.com/docs/connected-fields-api/reference/connectedfields.md) - [TabInfo](https://developers.docusign.com/docs/connected-fields-api/reference/connectedfields/tabinfo.md) ## API Docs - API Reference > ConnectedFields > TabInfo [Get connected fields tab groups](https://developers.docusign.com/docs/connected-fields-api/reference/connectedfields/tabinfo/getconnectedfieldstabgroups.md) ## OpenAPI Specification The raw OpenAPI 3.1 specification for this API is available at: - [OpenAPI JSON](https://developers.docusign.com/openapi.json) - [OpenAPI YAML](https://developers.docusign.com/openapi.yaml) > **Note:** This page contains both a page directory (above) and the landing page content (below). The page directory is generated for agent use and does not appear on the landing page. > You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL. > > Documentation indexes by section: > - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt > - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt > - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt > - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt > > Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth > Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks > > OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json > MCP server: https://docusign.docs.buildwithfern.com/_mcp/server # Connected Fields API overview > The Connected Fields API enables you to validate your envelope field data programmatically. The Connected Fields API lets developers discover custom, partner, or Docusign data models for [extension apps](https://apps.docusign.com/app-center) installed by their accounts. Data models supported today include [seven standard, Docusign-published Data Verification extensions](/extension-apps/extension-app-reference/extension-contracts), and custom models imported using the [Connected fields](/extension-apps/extension-apps-101/supported-extensions/connected-fields) extension type. Connected fields can now be added to envelopes via eSignature REST API by using the output of the Connected Fields API discovery endpoint. Accelerate agreement turnaround times and minimize errors with extension apps that verify and autofill data during signing. ## Places to start * [Discover connected fields concepts](/docs/connected-fields-api/concepts) * [See how to verify envelope fields programmatically](/docs/connected-fields-api/send-envelope-with-data-verification-fields) * [Explore the API Reference](/docs/connected-fields-api/reference) * [See how to integrate data verification using the Connected Fields API](https://players.brightcove.net/6118377982001/ZhVNgbpMt_default/index.html?videoId=6370599224112) ## Features #### Seamless access to data models Easily retrieve the Docusign, partner, or customer-defined data models used by your extension apps. Map and use these models in your eSignature REST API methods. #### Verify your envelope fields programmatically Map your envelope fields to your data verification or connected fields extensions to verify the data your recipients enter in real time. #### Reduce errors and manual input Improve accuracy, speed, and compliance by verifying and auto-filling recipient fields data during signing. ## Discover more * [See an example connected fields reference implementation](https://github.com/docusign/extension-app-connected-fields-reference-implementation) * [See an example data verification reference implementation](https://github.com/docusign/extension-app-data-verification-reference-implementation) * [Learn about connected fields extension apps](/extension-apps/extension-apps-101/supported-extensions/connected-fields) * [Watch a video on how to integrate data verification using the Connected Fields API](https://bcove.video/4l51CpM)