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

Clarifeye Users API

Manage users within a project

Clarifeye Users API is one of 13 APIs that Clarifeye 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.

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

Requests are made against 2 base URLs: https://eu.app.clarifeye.ai/api/v1, https://us.app.clarifeye.ai/api/v1.

3 operations 3 paths 6 schemas 1 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://eu.app.clarifeye.ai/api/v1
Authentication
HTTP Bearer, API Key
Contact
Clarifeye Support
Resource Areas
1

Authentication & Security 2

Clarifeye Users API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). An API key is passed in the header as Authorization (TokenAuth). By default, every request must be authenticated.

  • BearerAuth — Use Authorization: Bearer
  • TokenAuth — Use Authorization: Token

Paths & Operations 3

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

Users 3

Manage users within a project

GET
/projects/{project_id}/users/
List project users
listProjectUsers 4 params → 200401403404
POST
/projects/{project_id}/users/remove-by-email/
Remove user by email
removeUserByEmail 1 param body → 204400401403
PATCH
/projects/{project_id}/users/{permission_id}/
Update user permissions
updateUserPermissions 2 params body → 200400401403404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are PaginatedResponse (4 properties), ProjectPermission (3 properties), User (3 properties), Error (1 property). Each schema is shown below with its type and property counts.

ValidationError
object
User
object
3 properties
PermissionType
string
- CANPERFORMADMINACTIONS: Full administrative access - CANVIEWDATA: Read-only access to project data - CANRUNTASKS: Execute background tasks and pipelines - CA…
Error
object
1 property
ProjectPermission
object
3 properties
PaginatedResponse
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clarifeye-users-api-openapi.yml Raw ↑

Other APIs Clarifeye publishes across the network.

Clarifeye Agent Settings API
Clarifeye Conversations API
Clarifeye Documents API
Clarifeye Extraction Flows API
Clarifeye Feedback API
Clarifeye Interviews API
Clarifeye Invitations API
Clarifeye Notifications API
Clarifeye Pipeline Runs API
Clarifeye Signals API
Clarifeye Tables API
Clarifeye Tools API
Where this information came from

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