Den API
API by OpenWork · rest
OpenAPI spec for the Den control plane API. Authentication: - API keys (they start with den_) go in the x-api-key header as the raw value. Do not send them as Authorization: Bearer; that header only accepts Den session tokens, so an API key there returns 401. Example: curl https://api.openworklabs.com/v1/me -H "x-api-key: den_...". API keys resolve to the issuing user and the organization member they were scoped to when created, so they can call ordinary user and organization routes without a separate signed-in session. - Use Authorization: Bearer <session-token> for user-authenticated routes that require a Den session. - Session-only flows still require a signed-in user session, including organization creation, invitation acceptance, active-organization switching, and MCP token minting. - Public routes like health and documentation do not require authentication. Swagger tip: use the security schemes in the Authorize dialog to set denApiKey (your API key) or…
Endpoint: https://api.openworklabs.com/
Verification: observed. Source: crawl.
Capabilities (753)
- Get OAuth authorization server metadata
- Get OAuth authorization server metadata
- Get OAuth protected resource metadata for /mcp
- Get OAuth protected resource metadata for /mcp
- Get OAuth protected resource metadata for /mcp/admin
- Get OAuth protected resource metadata for /mcp/agent
- Get OAuth protected resource metadata for /mcp/agent
- Get OpenID Connect discovery document
- Get OpenID Connect discovery document
- Get OAuth authorization server metadata
- Get OpenID Connect discovery document
- Start an OAuth authorization request
- Register an OAuth client dynamically
- List SCIM groups
- Create a SCIM group
- Get a SCIM group
- Replace a SCIM group
- Patch a SCIM group
- Delete a SCIM group
- List SCIM resource types
- Get the SCIM Group resource type
- List SCIM schemas
- Create a SCIM user
- Replace a SCIM user
- Patch a SCIM user