Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/clarifeye:clarifeye-invitations-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Clarifeye Platform API — Full API Documentation Invitations…
description: 'Complete REST API reference for the Clarifeye Platform.
Documents every endpoint exposed by the platform — the public surface plus
the advanced surface: pipeline customization (extraction flows, pipeline
runs, warehouse tables, document tag/metadata configuration), the pre-MCP
AI surface (agent settings, playground conversations, conversation-scoped
feedback views, notifications), and the impersonation header. New AI
integrations should consume knowledge via MCP rather than the
conversation/agent-settings endpoints documented here.
## Authentication
All endpoints require authentication. Include the Authorization header in every request using either format:
- `Authorization: Token `
- `Authorization: Bearer `
## Service accounts and API keys
Integrations authenticate with an **API key** of a **service account**:
- `Authorization: Bearer ` (keys start with `cfk_`)
A service account is an ordinary member (role `member`) of one organization that cannot log
in. Organization admins create it and mint its keys on the organization''s *Service
accounts* page (`/organizations/{id}/service-accounts/`, `/organization-api-keys/`), and
give it access to knowledge stores with ordinary store permissions. A key is valid on every
endpoint and acts as its service account: it reaches exactly the stores, with exactly the
rights, the account was given. An account can hold several keys (each with its own name,
optional expiry and revocation), so a key can be rotated without changing identity.
A refused key answers **403** with one of: `Invalid API key.`, `API key revoked.`,
`API key expired.`, `API key disabled.` (the service account is disabled).
Any valid key may also call `POST /organizations/{id}/provision-user/` and
`POST /organizations/{id}/deprovision-user/` for its own organization (the `{id}` in the
path must be the key''s organization). The email domains these may pre-create accounts for
are configured by Clarifeye on the organization (`allowed_provisioning_domains`).
## Impersonation
Certain endpoints support user impersonation for creating or listing data on behalf of other users.
This is useful for integrating external systems that need to attribute actions to specific users.
**Header:** `X-Impersonate-Email`
**Required Permission:** `CAN_IMPERSONATE_OTHER_USERS` (for a person, contact Clarifeye to enable it; org admins grant it to a service account on the organization''s Service accounts page)
**Behavior:**
- If the header is provided and the impersonator has the required permission, the action is performed as the target user
- If the target user is not found, the request proceeds as the original authenticated user
- If the target user does not have access to the project, the request proceeds as the original authenticated user
- If the impersonator lacks the `CAN_IMPERSONATE_OTHER_USERS` permission, the header is ignored
**With an API key** the request fails instead (**403**) whenever impersonation cannot
happen: missing permission, unknown target, target without access to the store, target that
is itself a service account, or an endpoint outside a store. A key never silently acts as
its own service account when impersonation was asked for.'
version: 1.0.0
contact:
name: Clarifeye Support
servers:
- url: https://eu.app.clarifeye.ai/api/v1
description: EU
- url: https://us.app.clarifeye.ai/api/v1
description: US
security:
- BearerAuth: []
- TokenAuth: []
tags:
- name: Invitations
description: Manage project invitations
paths:
/projects/{project_id}/invites/:
get:
tags:
- Invitations
summary: List invitations
description: Retrieve all invitations for a project with optional filtering by status.
operationId: listInvitations
parameters:
- $ref: '#/components/parameters/ProjectId'
- name: status
in: query
description: Filter by invitation status
schema:
$ref: '#/components/schemas/InvitationStatus'
- name: search
in: query
description: Filter by email (case-insensitive partial match)
schema:
type: string
- $ref: '#/components/parameters/Limit'
- $ref: '#/components/parameters/Offset'
responses:
'200':
description: Successful response
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/PaginatedResponse'
- type: object
properties:
results:
type: array
items:
$ref: '#/components/schemas/ProjectInvite'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
/projects/{project_id}/invites/invite/:
post:
tags:
- Invitations
summary: Invite user to project
description: 'Invite a user to join the project.
- For new users (not registered): Creates a pending invite and sends an email.
- For existing users: Automatically accepts the invite and sends a notification.'
operationId: inviteUser
parameters:
- $ref: '#/components/parameters/ProjectId'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- email
- permissions
properties:
email:
type: string
format: email
description: Email address of the user to invite
example: user@example.com
permissions:
type: array
items:
$ref: '#/components/schemas/PermissionType'
description: Permissions to grant to the user
example:
- CAN_VIEW_DATA
- CAN_PERFORM_ADMIN_ACTIONS
profile:
allOf:
- $ref: '#/components/schemas/ProjectProfile'
description: 'Profile to assign to the invited user on the project.
Defaults to `contributor` when omitted.
'
responses:
'201':
description: Invitation created successfully
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/ProjectInvite'
- type: object
properties:
type:
type: string
enum:
- new_user
- existing_user
description: '- `new_user`: User not registered, invite is pending
- `existing_user`: User exists, invite auto-accepted
'
'400':
description: Bad request - invalid permissions, user already invited, user already has access, or a service-account email (service accounts are managed on the organization's Service accounts page)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
/projects/{project_id}/invites/bulk-invite/:
post:
tags:
- Invitations
summary: Bulk invite users to project
description: 'Invite up to 100 email addresses in one call, all with the same
permissions and profile. Each email is processed independently
(partial success): existing users are added immediately, new users get
a pending invite and a signup email, and rejected addresses (invalid,
already a member, already invited, domain not allowed) are skipped
without failing the batch. Duplicates within the batch are
deduplicated case-insensitively. Requires admin permissions on the
project.'
operationId: bulkInviteUsers
parameters:
- $ref: '#/components/parameters/ProjectId'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- emails
- permissions
properties:
emails:
type: array
maxItems: 100
items:
type: string
format: email
description: Email addresses to invite
example:
- alice@example.com
- bob@example.com
permissions:
type: array
items:
$ref: '#/components/schemas/PermissionType'
description: Permissions granted to every invited user
example:
- CAN_VIEW_DATA
profile:
allOf:
- $ref: '#/components/schemas/ProjectProfile'
description: 'Profile assigned to every invited user.
Defaults to `contributor` when omitted.
'
responses:
'200':
description: Per-email outcomes (returned even when some or all emails were skipped)
content:
application/json:
schema:
$ref: '#/components/schemas/BulkInviteResponse'
'400':
description: Bad request - malformed emails list, more than 100 emails, or invalid permissions/profile
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
/projects/{project_id}/invites/{invite_id}/:
patch:
tags:
- Invitations
summary: Edit a pending invitation
description: 'Change the permissions/profile a pending invitation will grant on
acceptance. Only pending invitations can be edited — accepted ones are
audit records whose live access lives on the membership, so editing one
returns 409. The email address is immutable: repointing an invitation at
a different person is a cancel-and-reinvite. Requires
CAN_PERFORM_ADMIN_ACTIONS.'
operationId: updateInvitation
parameters:
- $ref: '#/components/parameters/ProjectId'
- name: invite_id
in: path
required: true
description: UUID of the invitation
schema:
type: string
format: uuid
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
permissions:
type: array
items:
$ref: '#/components/schemas/PermissionType'
profile:
$ref: '#/components/schemas/ProjectProfile'
responses:
'200':
description: Invitation updated
content:
application/json:
schema:
$ref: '#/components/schemas/ProjectInvite'
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'409':
description: Invitation is no longer pending
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
delete:
tags:
- Invitations
summary: Cancel invitation
description: Cancel a pending invitation. Only pending invitations can be cancelled.
operationId: cancelInvitation
parameters:
- $ref: '#/components/parameters/ProjectId'
- name: invite_id
in: path
required: true
description: UUID of the invitation
schema:
type: string
format: uuid
responses:
'204':
description: Invitation cancelled successfully
'400':
description: Cannot cancel non-pending invitation
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
components:
schemas:
ProjectInvite:
type: object
properties:
id:
type: string
format: uuid
email:
type: string
format: email
permissions:
type: array
items:
$ref: '#/components/schemas/PermissionType'
profile:
$ref: '#/components/schemas/ProjectProfile'
status:
$ref: '#/components/schemas/InvitationStatus'
created_at:
type: string
format: date-time
updated_at:
type: string
format: date-time
invited_by:
$ref: '#/components/schemas/User'
assigned_interview_count:
type: integer
description: 'Interviews still waiting on this invitation. Non-zero means the
invitation exists to deliver an interview, so removing
CAN_TAKE_INTERVIEW would leave the invitee notified but unable to
open it.
'
PaginatedResponse:
type: object
properties:
count:
type: integer
description: Total number of results
next:
type:
- string
- 'null'
format: uri
description: URL to next page of results
previous:
type:
- string
- 'null'
format: uri
description: URL to previous page of results
results:
type: array
items: {}
BulkInviteResult:
type: object
properties:
email:
type: string
description: Normalized (lowercased) email address from the request
status:
type: string
enum:
- invited_new
- added_existing
- skipped
description: '- `invited_new`: pending invite created, signup email sent
- `added_existing`: existing user added immediately
- `skipped`: nothing done, see `reason`
'
reason:
type:
- string
- 'null'
enum:
- invalid_email
- already_member
- pending_invite
- domain_not_allowed
- error
description: 'Why the email was skipped; null unless status is `skipped`.
`error` means an unexpected failure was contained to this address so
the rest of the batch could proceed.
'
User:
type: object
properties:
id:
type: string
format: uuid
email:
type: string
format: email
display_name:
type:
- string
- 'null'
description: Name to show instead of the email. Set for service accounts, null for people.
is_service_account:
type: boolean
date_joined:
type: string
format: date-time
InvitationStatus:
type: string
enum:
- pending
- accepted
- cancelled
description: '- `pending`: Invitation sent, awaiting response
- `accepted`: User accepted the invitation
- `cancelled`: Invitation was cancelled
'
BulkInviteResponse:
type: object
properties:
results:
type: array
description: Per-email outcomes, in request order after deduplication
items:
$ref: '#/components/schemas/BulkInviteResult'
invited_new:
type: integer
added_existing:
type: integer
skipped:
type: integer
ProjectProfile:
type: string
enum:
- tech
- contributor
- user
default: contributor
description: 'Profile of the user on the project. The profile shapes the UI surface a
user sees (sidebar, available views) and complements the fine-grained
`permissions` list.
- `tech`: Technical profile with access to advanced/technical interfaces
- `contributor`: Default profile for users who contribute to the project
- `user`: End-user profile with the most restricted UI surface
'
PermissionType:
type: string
enum:
- CAN_PERFORM_ADMIN_ACTIONS
- CAN_VIEW_DATA
- CAN_IMPERSONATE_OTHER_USERS
description: '- `CAN_PERFORM_ADMIN_ACTIONS`: Full administrative access
- `CAN_VIEW_DATA`: Read-only access to project data
- `CAN_IMPERSONATE_OTHER_USERS`: Impersonate other users in API calls (for a person, contact Clarifeye to enable it; org admins grant it to a service account)
'
Error:
type: object
properties:
error:
type: string
description: Error message
example:
error: User not found
ValidationError:
type: object
additionalProperties:
type: array
items:
type: string
example:
email:
- This field is required.
parameters:
ProjectId:
name: project_id
in: path
required: true
description: UUID of the project
schema:
type: string
format: uuid
Offset:
name: offset
in: query
description: Number of results to skip for pagination
schema:
type: integer
default: 0
minimum: 0
Limit:
name: limit
in: query
description: Maximum number of results per page
schema:
type: integer
default: 100
minimum: 1
maximum: 1000
responses:
NotFound:
description: Not found - resource does not exist
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
example:
error: Not found.
Unauthorized:
description: Unauthorized - missing or invalid authentication
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
example:
error: Authentication credentials were not provided.
Forbidden:
description: Forbidden - insufficient permissions
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
example:
error: You do not have permission to perform this action.
BadRequest:
description: Bad request - invalid parameters or request body
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/Error'
- $ref: '#/components/schemas/ValidationError'
securitySchemes:
BearerAuth:
type: http
scheme: bearer
description: 'Use `Authorization: Bearer <token>`. The token is either a user token / OAuth access
token, or a service-account API key (`cfk_...`). A key is valid on every endpoint and
acts as its service account, an organization member with per-store permissions.
Refused keys answer 403 with `Invalid API key.`, `API key revoked.`,
`API key expired.` or `API key disabled.`.
'
TokenAuth:
type: apiKey
in: header
name: Authorization
description: 'Use Authorization: Token <token>'
x-tagGroups:
- name: Extractors
tags:
- Object Extractors
- Tag Extractors
- Chunks Extractors
- Parsing Extractors
- Document Filter Extractors
- Chunk Tag Filter Extractors
- Document Tag Extractors
- Tag Alerts Extractors
- Object Alerts Extractors
- Imported Object Extractors
x-provenance:
method: harvested
publisher: Clarifeye
source: https://docs.clarifeye.ai/api-reference/openapi-full.yaml
note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
stamped by stamp-openapi-provenance.py (roadmap#793)