Docusign · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for DocuSign REST Account Permission Profiles API

6 actions 6 updates phrasing extends openapi/docusign-accountpermissionprofiles-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 6

$.info
$.paths['/v2/accounts/{accountId}/permission_profiles'].get
$.paths['/v2/accounts/{accountId}/permission_profiles'].post
$.paths['/v2/accounts/{accountId}/permission_profiles/{permissionProfileId}'].get
$.paths['/v2/accounts/{accountId}/permission_profiles/{permissionProfileId}'].put
$.paths['/v2/accounts/{accountId}/permission_profiles/{permissionProfileId}'].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 Account Permission Profiles API
  version: 1.0.0
extends: openapi/docusign-accountpermissionprofiles-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: 5
- target: $.paths['/v2/accounts/{accountId}/permission_profiles'].get
  update:
    x-apievangelist-phrasing:
      intent: List permission profiles
      effect: read
      questions:
      - What permission profiles exist on my account?
      - Can I see which users are assigned to each permission profile?
      instructions:
      - text: List the permission profiles for account {account}.
        slots:
          account: path.accountId
      - text: List permission profiles in account {account} including {include}.
        slots:
          account: path.accountId
          include: query.include
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/permission_profiles'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a permission profile
      effect: write
      questions:
      - How do I create a new set of user permissions I can assign to people?
      - Can I define settings for a new permission profile up front?
      instructions:
      - text: Create a permission profile named {permissionProfileName} in account {account}.
        slots:
          permissionProfileName: requestBody.permissionProfileName
          account: path.accountId
      - text: Create permission profile {permissionProfileName} with settings {settings}.
        slots:
          permissionProfileName: requestBody.permissionProfileName
          settings: requestBody.settings
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/permission_profiles/{permissionProfileId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get one permission profile
      effect: read
      questions:
      - What settings does a specific permission profile grant?
      - Who is assigned to a given permission profile?
      instructions:
      - text: Get permission profile {profile} in account {account}.
        slots:
          profile: path.permissionProfileId
          account: path.accountId
      - text: Show the settings of permission profile {profile}.
        slots:
          profile: path.permissionProfileId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/permission_profiles/{permissionProfileId}'].put
  update:
    x-apievangelist-phrasing:
      intent: Update a permission profile
      effect: write
      questions:
      - How do I rename an existing permission profile?
      - Can I change the settings on a permission profile already in use?
      instructions:
      - text: Rename permission profile {profile} in account {account} to {permissionProfileName}.
        slots:
          profile: path.permissionProfileId
          account: path.accountId
          permissionProfileName: requestBody.permissionProfileName
      - text: Update the settings of permission profile {profile} to {settings}.
        slots:
          profile: path.permissionProfileId
          settings: requestBody.settings
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/accounts/{accountId}/permission_profiles/{permissionProfileId}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a permission profile
      effect: destructive
      questions:
      - What happens to users when I delete their permission profile?
      - Can I move users to another profile while deleting one?
      instructions:
      - text: Delete permission profile {profile} from account {account}.
        slots:
          profile: path.permissionProfileId
          account: path.accountId
      - text: Delete permission profile {profile} and move its users to {move_users_to}.
        slots:
          profile: path.permissionProfileId
          move_users_to: query.move_users_to
      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-accountpermissionprofiles-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.