Docusign Roles API
Each role is associated with specific permissions. Each new member is assigned a role when you create them, automatically granting them the permissions associated with that role.Roles use the following permission types to control the actions that users can perform:- Room- Room Details- Documents- Envelopes- Member Management- Company SettingsRooms enables you to configure custom roles containing permissions that make sense for your company. Because each new member is assigned a role, you must set up these roles before you can invite members to join your account.Permissions for roles are tied to the `roleId` property and not yet exposed. You can learn more about these permission types and configure them in the console.### Internal and External RolesIn Rooms, a role can be either internal or external. You assign internal roles to people inside your company. You assign external roles to people outside your company when you invite them to a room.Each member inside your company has a default company role. However, they can also be assigned additional roles with different permissions on a per-room basis. Regardless of the member's default company role, what they can do in a room is entirely controlled by their role in that particular room.
Docusign Roles API is one of 134 APIs that Docusign publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
This API exposes 1 JSON Schema definition.
Tagged areas include Roles. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, a JSON-LD context, a getting-started guide, rate-limit docs, and 1 JSON Schema.
This API exposes 5 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version v2.
Requests are made against a single base URL, https://rooms.docusign.com/restapi.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Docusign Roles API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as Authorization (Bearer).
By default, every request must be authenticated.
Bearer— JWT Authorization header using the Bearer scheme. Example: "Authorization: Bearer {token}"
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Each role is associated with specific permissions. Each new member is assigned a role when you create them, automatically granting them the permissions associated with that role.…
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Permissions (66 properties), Role (8 properties), RoleSummaryList (7 properties), RoleSummary (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Docusign 12
Other APIs Docusign publishes across the network.
This is an independent, third-party profile of Docusign Roles API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.