Docusign · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for DocuSign REST Envelope Consumer Disclosures API

3 actions 3 updates phrasing extends openapi/docusign-envelopeconsumerdisclosures-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Docusign's API. It is a proposal applied on top of the contract, not a document Docusign publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info
$.paths['/v2/accounts/{accountId}/envelopes/{envelopeId}/recipients/{recipientId}/consumer_disclosure'].get
$.paths['/v2/accounts/{accountId}/envelopes/{envelopeId}/recipients/{recipientId}/consumer_disclosure/{langCode}'].get

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for DocuSign REST Envelope Consumer Disclosures API
  version: 1.0.0
extends: openapi/docusign-envelopeconsumerdisclosures-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 2
- target: $.paths['/v2/accounts/{accountId}/envelopes/{envelopeId}/recipients/{recipientId}/consumer_disclosure'].get
  update:
    x-apievangelist-phrasing:
      intent: Get the disclosure shown to an envelope recipient
      effect: read
      questions:
      - Which e-signature disclosure did a recipient on my envelope see?
      - Can I request a recipient's disclosure in a different language with a query option?
      instructions:
      - text: Get the consumer disclosure for recipient {recipient} on envelope {envelope} in account {account}.
        slots:
          recipient: path.recipientId
          envelope: path.envelopeId
          account: path.accountId
      - text: Show recipient {recipient}'s signing disclosure for envelope {envelope} in language {lang}.
        slots:
          recipient: path.recipientId
          envelope: path.envelopeId
          lang: query.langCode
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/envelopes/{envelopeId}/recipients/{recipientId}/consumer_disclosure/{langCode}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a recipient's disclosure by language code
      effect: read
      questions:
      - Can I fetch an envelope recipient's disclosure for a language set in the path?
      - Is the language-coded recipient disclosure endpoint reserved?
      instructions:
      - text: Fetch the reserved path-language {lang} disclosure version for signer {recipient} of envelope {envelope}, account {account}.
        slots:
          lang: path.langCode
          recipient: path.recipientId
          envelope: path.envelopeId
          account: path.accountId
      - text: Show the language-coded {lang} disclosure that recipient {recipient} would see.
        slots:
          lang: path.langCode
          recipient: path.recipientId
      method: generated
      generated: '2026-10-01'

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/docusign-envelopeconsumerdisclosures-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.