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

OPAQUE Users API is one of 11 APIs that OPAQUE publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 7 operations across 5 paths. It is described by OpenAPI 3.2.0, at version 2.5.

Requests are made against a single base URL, http://localhost:5001/.

7 operations 5 paths 0 schemas 1 DELETE4 GET2 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.5
Base URL
https://api./v2.5
Authentication
HTTP Bearer, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 4

OPAQUE Users API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (sessionToken). An API key is passed in the cookie as userIdentitySecret (userIdentitySecret). An API key is passed in the cookie as sessionTokenCookie (sessionTokenCookie). An API key is passed in the cookie as refreshTokenCookie (refreshTokenCookie). By default, every request must be authenticated.

  • sessionToken — The bearer token is obtained from the /login and /register endpoints.
  • userIdentitySecret — A binary blob derived from a user's passkey. It can be obtained from the /login and /register endpoints.

Paths & Operations 7

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

users 7

Users

GET
/{version}/user
Get user
get_user 1 param → 200
PATCH
/{version}/user
Update user
update_user 1 param body → 200
DELETE
/{version}/user
Delete user
delete_user 1 param → 200
GET
/{version}/user/exists
Check user existence
check_user_exists 1 param → 200
GET
/{version}/user/keys
Get user keys
get_user_keys 1 param → 200
PATCH
/{version}/user/organization-roles
Update another user's organization roles
update_user_organization_roles 1 param body → 200400
GET
/{version}/workspaces/members
Get shared workspace members
get_shared_workspace_members 1 param → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opaque-users-api-openapi.yml Raw ↑

Other APIs OPAQUE publishes across the network.

OPAQUE Asset Configs API
OPAQUE Auth API
OPAQUE Datasets API
OPAQUE Jobs API
OPAQUE Organizations API
OPAQUE Pinned Queries API
OPAQUE Predefined Query Templates API
OPAQUE Versioning API
OPAQUE Workflows API
OPAQUE Workspaces API
Where this information came from

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