How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Coda Project Doc Permissions API

This API lets you manage sharing and permissions for your docs.

Coda Project Doc Permissions API is one of 32 APIs that Coda Project publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Doc Permissions. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 6 operations across 4 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 0.0.2.

Requests are made against a single base URL, https://docs.superhuman.com/apis/admin/v1.

6 operations 4 paths 21 schemas 2 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.2
Base URL
https://coda.io/apis/v1
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Coda Project Doc Permissions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (UUID) (Bearer). By default, every request must be authenticated.

  • Bearer — The Superhuman Docs Admin API can be accessed using an API token, which can be obtained from [My account](https://docs.superhuman.com/account) in Superhuman Do…

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 2 DELETE, 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Doc Permissions 6

This API lets you manage sharing and permissions for your docs.

GET
/organizations/{organizationId}/workspaces/{workspaceId}/docs/{docId}/acl/permissions
List doc permissions
listDocPermissionsV2 5 params → 200400401403404429
POST
/organizations/{organizationId}/workspaces/{workspaceId}/docs/{docId}/acl/permissions
Add permission to a doc
addDocPermissionV2 3 params body → 200400401403404429
DELETE
/organizations/{organizationId}/workspaces/{workspaceId}/docs/{docId}/acl/permissions/{docPermissionId}
Delete doc permission
deleteDocPermissionV2 4 params → 200400401403404429
GET
/organizations/{organizationId}/docs/{docId}/acl/permissionsdeprecated
List doc permissions
listDocPermissions 4 params → 200400401403404429
POST
/organizations/{organizationId}/docs/{docId}/acl/permissionsdeprecated
Add permission to a doc
addDocPermission 2 params body → 200400401403404429
DELETE
/organizations/{organizationId}/docs/{docId}/acl/permissions/{docPermissionId}deprecated
Delete doc permission
deleteDocPermission 3 params → 200400401403404429

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are AddPermissionRequest (4 properties), Permission (4 properties), Acl (4 properties), GroupPrincipal (3 properties). Each schema is shown below with its type and property counts.

AccessTypeNotNone
string
Type of access (excluding none).
AddPermissionResult
object
The result of adding a permission.
AnyonePrincipal
object
1 property 1 required
AddedGroupPrincipal
object
2 properties 2 required
AddedDomainPrincipal
object
2 properties 2 required
GroupPrincipal
object
3 properties 3 required
DomainPrincipal
object
2 properties 2 required
NextPageLink
string
If specified, a link that can be used to fetch the next page of results.
AddedEmailPrincipal
object
2 properties 2 required
AddedPrincipal
Metadata about a principal to add to a doc.
Permission
object
A specific permission granted to a principal.
4 properties 4 required
AccessType
string
Type of access.
DeletePermissionResult
object
The result of deleting a permission.
Acl
object
Paginated list of Permissions.
4 properties 1 required
AddedWorkspacePrincipal
object
2 properties 2 required
AddedAnyonePrincipal
object
1 property 1 required
Principal
Metadata about a principal.
EmailPrincipal
object
2 properties 2 required
AddPermissionRequest
object
Payload for granting a new permission.
4 properties 2 required
WorkspacePrincipal
object
2 properties 2 required
NextPageToken
string
If specified, an opaque token used to fetch the next page of results.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

coda-project-doc-permissions-api-openapi.yml Raw ↑

Other APIs Coda Project publishes across the network.

Coda Project Account API
Coda Project Analytics API
Coda Project API Tokens API
Coda Project Automations API
Coda Project Columns API
Coda Project Controls API
Coda Project CustomDocDomains API
Coda Project Doc Export API
Coda Project Docs API
Coda Project Events API
Coda Project Folder Permissions API
Coda Project Folders API
Where this information came from

This is an independent, third-party profile of Coda Project Doc Permissions 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.