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

Openwork Roles API

Organization custom role management routes.

Openwork Roles API is one of 37 APIs that Openwork publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Roles. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version dev.

Requests are made against a single base URL, https://api.openworklabs.com.

3 operations 2 paths 5 schemas 1 DELETE1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
dev
Base URL
https://api.openworklabs.com
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Openwork Roles API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (session-token) (bearerAuth). An API key is passed in the header as x-api-key (denApiKey).

  • bearerAuth — Session token passed as Authorization: Bearer for user-authenticated Den routes.
  • denApiKey — Organization API key passed as the x-api-key header for API-key-authenticated Den routes.

Paths & Operations 3

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

Roles 3

Organization custom role management routes.

POST
/v1/roles
Create organization role
postV1Roles body → 201400401403404
PATCH
/v1/roles/{roleId}
Update organization role
patchV1RolesByRoleId 1 param body → 200400401403404
DELETE
/v1/roles/{roleId}
Delete organization role
deleteV1RolesByRoleId 1 param → 204400401403404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ForbiddenError (3 properties), NotFoundError (2 properties), InvalidRequestError (2 properties), UnauthorizedError (1 property). Each schema is shown below with its type and property counts.

InvalidRequestError
object
2 properties 2 required
NotFoundError
object
2 properties 1 required
ForbiddenError
object
3 properties 1 required
SuccessResponse
object
1 property 1 required
UnauthorizedError
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openwork-roles-api-openapi.yml Raw ↑

Other APIs Openwork publishes across the network.

Openwork Admin API
Openwork API Keys API
Openwork Auth API
Openwork Authentication API
Openwork Bootstrap API
Openwork Capability Sources API
Openwork Config Objects API
Openwork Connectors API
Openwork Desktop Policies API
Openwork Dev API
Openwork Diagnostics API
Openwork GitHub API
Where this information came from

This is an independent, third-party profile of Openwork 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.