Docusign · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for DocuSign REST Connect Events API

9 actions 9 updates phrasing extends openapi/docusign-connectevents-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 9

$.info
$.paths['/v2/accounts/{accountId}/connect/envelopes/{envelopeId}/retry_queue'].put
$.paths['/v2/accounts/{accountId}/connect/envelopes/retry_queue'].put
$.paths['/v2/accounts/{accountId}/connect/failures'].get
$.paths['/v2/accounts/{accountId}/connect/failures/{failureId}'].delete
$.paths['/v2/accounts/{accountId}/connect/logs'].get
$.paths['/v2/accounts/{accountId}/connect/logs'].delete
$.paths['/v2/accounts/{accountId}/connect/logs/{logId}'].get
$.paths['/v2/accounts/{accountId}/connect/logs/{logId}'].delete

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 Connect Events API
  version: 1.0.0
extends: openapi/docusign-connectevents-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: 8
- target: $.paths['/v2/accounts/{accountId}/connect/envelopes/{envelopeId}/retry_queue'].put
  update:
    x-apievangelist-phrasing:
      intent: Republish Connect events for one envelope
      effect: write
      questions:
      - Can I resend the Connect webhook for a single envelope?
      - How do I retry a failed Connect notification for one envelope?
      instructions:
      - text: Republish Connect data for envelope {envelope} in account {account}.
        slots:
          envelope: path.envelopeId
          account: path.accountId
      - text: Retry the Connect post for envelope {envelope} on account {account}.
        slots:
          envelope: path.envelopeId
          account: path.accountId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/connect/envelopes/retry_queue'].put
  update:
    x-apievangelist-phrasing:
      intent: Republish Connect events for many envelopes
      effect: write
      questions:
      - Is there a way to republish Connect failures for a batch of envelopes?
      - Can a Connect republish run synchronously?
      instructions:
      - text: Republish Connect for envelopes {envelope_ids} in account {account}.
        slots:
          envelope_ids: requestBody.envelopeIds
          account: path.accountId
      - text: 'Retry Connect posts for these failed envelopes in account {account}: {envelope_ids}.'
        slots:
          account: path.accountId
          envelope_ids: requestBody.envelopeIds
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/connect/failures'].get
  update:
    x-apievangelist-phrasing:
      intent: List Connect delivery failures
      effect: read
      questions:
      - Which envelopes failed to post to my Connect listener?
      - Can I see Connect failures within a date range?
      instructions:
      - text: List Connect failures in account {account}.
        slots:
          account: path.accountId
      - text: Show Connect post failures for account {account} between {from_date} and {to_date}.
        slots:
          account: path.accountId
          from_date: query.from_date
          to_date: query.to_date
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/connect/failures/{failureId}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a Connect failure log entry
      effect: destructive
      questions:
      - Can I clear a single entry from the Connect failure log?
      - How do I remove a resolved Connect failure record?
      instructions:
      - text: Delete Connect failure entry {failure} in account {account}.
        slots:
          failure: path.failureId
          account: path.accountId
      - text: Remove failure record {failure} from account {account}'s Connect failure log.
        slots:
          failure: path.failureId
          account: path.accountId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/connect/logs'].get
  update:
    x-apievangelist-phrasing:
      intent: List Connect log entries
      effect: read
      questions:
      - Where can I review the Connect log entries for my account?
      - Why would the Connect log be empty?
      instructions:
      - text: List the Connect log entries for account {account}.
        slots:
          account: path.accountId
      - text: Show Connect logs for account {account} from {from_date} to {to_date}.
        slots:
          account: path.accountId
          from_date: query.from_date
          to_date: query.to_date
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/connect/logs'].delete
  update:
    x-apievangelist-phrasing:
      intent: Clear the entire Connect log
      effect: destructive
      questions:
      - Can I wipe all Connect log entries for my account at once?
      - Is there a call to purge the whole Connect log?
      instructions:
      - text: Delete all Connect log entries in account {account}.
        slots:
          account: path.accountId
      - text: Purge the full Connect log for account {account}.
        slots:
          account: path.accountId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/connect/logs/{logId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get one Connect log entry
      effect: read
      questions:
      - How do I inspect a single Connect log entry in detail?
      - Can I get extra info about one Connect delivery attempt?
      instructions:
      - text: Get Connect log entry {log} in account {account}.
        slots:
          log: path.logId
          account: path.accountId
      - text: Show the details of Connect log {log} for account {account}.
        slots:
          log: path.logId
          account: path.accountId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/connect/logs/{logId}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete one Connect log entry
      effect: destructive
      questions:
      - Can I delete just one entry from the Connect log?
      - Which call removes a specific Connect log record?
      instructions:
      - text: Delete Connect log entry {log} from account {account}.
        slots:
          log: path.logId
          account: path.accountId
      - text: Remove log {log} from account {account}'s Connect log.
        slots:
          log: path.logId
          account: path.accountId
      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-connectevents-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.