Clarifeye Notifications API
Manage project-scoped notifications for users
Manage project-scoped notifications for users
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/clarifeye:clarifeye-notifications-api"
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.
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: 3.2.0
info:
title: Clarifeye Platform API — Full API Documentation…
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: Notifications
description: Manage project-scoped notifications for users
paths:
/projects/{project_id}/notifications/:
get:
tags:
- Notifications
summary: List project notifications
description: 'List notifications for the effective user (authenticated user or impersonated user).
**Filtering:**
- Only PROJECT-scoped notifications are returned (not account-level)
- Returns all unread notifications plus read notifications from the last 7 days
- Optionally filter by status using the `status` query parameter
**Impersonation:**
When using the `X-Impersonate-Email` header, returns notifications for the target user
instead of the authenticated user.'
operationId: listProjectNotifications
parameters:
- $ref: '#/components/parameters/ProjectId'
- $ref: '#/components/parameters/ImpersonateEmail'
- name: status
in: query
description: Filter by notification status
schema:
$ref: '#/components/schemas/NotificationStatus'
- $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/ProjectScopedNotification'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
/projects/{project_id}/notifications/{notification_id}/:
get:
tags:
- Notifications
summary: Retrieve a notification
description: 'Retrieve details of a single notification for the effective user.
**Impersonation:**
When using the `X-Impersonate-Email` header, retrieves the notification for the target user.'
operationId: getProjectNotification
parameters:
- $ref: '#/components/parameters/ProjectId'
- $ref: '#/components/parameters/NotificationId'
- $ref: '#/components/parameters/ImpersonateEmail'
responses:
'200':
description: Successful response
content:
application/json:
schema:
$ref: '#/components/schemas/ProjectScopedNotification'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
delete:
tags:
- Notifications
summary: Delete a notification
description: 'Delete a single notification for the effective user.
**Impersonation:**
When using the `X-Impersonate-Email` header, deletes the notification for the target user.'
operationId: deleteProjectNotification
parameters:
- $ref: '#/components/parameters/ProjectId'
- $ref: '#/components/parameters/NotificationId'
- $ref: '#/components/parameters/ImpersonateEmail'
responses:
'204':
description: Notification deleted successfully
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
/projects/{project_id}/notifications/{notification_id}/mark-as-read/:
post:
tags:
- Notifications
summary: Mark notification as read
description: 'Mark a single notification as read for the effective user.
**Impersonation:**
When using the `X-Impersonate-Email` header, marks the notification as read for the target user.'
operationId: markNotificationAsRead
parameters:
- $ref: '#/components/parameters/ProjectId'
- $ref: '#/components/parameters/NotificationId'
- $ref: '#/components/parameters/ImpersonateEmail'
responses:
'200':
description: Notification marked as read
content:
application/json:
schema:
$ref: '#/components/schemas/ProjectScopedNotification'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
/projects/{project_id}/notifications/{notification_id}/mark-as-unread/:
post:
tags:
- Notifications
summary: Mark notification as unread
description: 'Mark a single notification as unread for the effective user.
**Impersonation:**
When using the `X-Impersonate-Email` header, marks the notification as unread for the target user.'
operationId: markNotificationAsUnread
parameters:
- $ref: '#/components/parameters/ProjectId'
- $ref: '#/components/parameters/NotificationId'
- $ref: '#/components/parameters/ImpersonateEmail'
responses:
'200':
description: Notification marked as unread
content:
application/json:
schema:
$ref: '#/components/schemas/ProjectScopedNotification'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
/projects/{project_id}/notifications/mark-all-as-read/:
post:
tags:
- Notifications
summary: Mark all notifications as read
description: 'Mark all unread project notifications as read for the effective user.
**Impersonation:**
When using the `X-Impersonate-Email` header, marks all notifications as read for the target user.'
operationId: markAllNotificationsAsRead
parameters:
- $ref: '#/components/parameters/ProjectId'
- $ref: '#/components/parameters/ImpersonateEmail'
responses:
'200':
description: All notifications marked as read
content:
application/json:
schema:
$ref: '#/components/schemas/NotificationBulkActionResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
/projects/{project_id}/notifications/delete-read/:
post:
tags:
- Notifications
summary: Delete all read notifications
description: 'Delete all read project notifications for the effective user.
**Impersonation:**
When using the `X-Impersonate-Email` header, deletes all read notifications for the target user.'
operationId: deleteReadNotifications
parameters:
- $ref: '#/components/parameters/ProjectId'
- $ref: '#/components/parameters/ImpersonateEmail'
responses:
'200':
description: All read notifications deleted
content:
application/json:
schema:
$ref: '#/components/schemas/NotificationBulkActionResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
components:
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
ImpersonateEmail:
name: X-Impersonate-Email
in: header
required: false
description: 'Email of the user to impersonate. Requires `CAN_IMPERSONATE_OTHER_USERS` permission.
If the target user is not found or does not have access to the project, the request
proceeds as the authenticated user. Contact Clarifeye to enable this permission.
'
schema:
type: string
format: email
NotificationId:
name: notification_id
in: path
required: true
description: UUID of the notification
schema:
type: string
format: uuid
schemas:
NotificationStatus:
type: string
enum:
- unread
- read
description: '- `unread`: Notification has not been read
- `read`: Notification has been read
'
NotificationBase:
type: object
description: Base notification properties shared by all notification types
properties:
id:
type: string
format: uuid
description: Unique identifier for the notification
created_at:
type: string
format: date-time
description: When the notification was created
updated_at:
type: string
format: date-time
description: When the notification was last updated
user:
type: string
format: uuid
description: ID of the user this notification belongs to
status:
$ref: '#/components/schemas/NotificationStatus'
access_level:
$ref: '#/components/schemas/NotificationAccessLevel'
title:
type: string
description: Notification title
example: Document processing completed
message:
type: string
description: Notification message body
example: Your document 'Q4 Report.pdf' has been processed successfully.
notification_type:
type: string
description: Type/category of the notification
example: document_processed
actions:
type: object
description: 'Optional actions that can be taken from the notification.
Structure may include:
- `primary`: Primary action with `label` and `type`
- `secondary`: Array of secondary actions
'
example:
primary:
label: View Document
type: navigate
url: /documents/123
read_at:
type:
- string
- 'null'
format: date-time
description: When the notification was marked as read (null if unread)
source_object_type:
type: string
description: Type of the source object that triggered this notification
example: document
source_object_id:
type: string
description: ID of the source object that triggered this notification
example: 550e8400-e29b-41d4-a716-446655440000
relative_time:
type: string
description: Human-readable relative time (e.g., "2 minutes ago", "Yesterday")
example: 2 hours ago
absolute_time:
type: string
format: date-time
description: ISO format absolute timestamp
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: {}
ProjectScopedNotification:
description: 'A project-scoped notification. Returned by project notification endpoints.
The `scope` is always "project" and `project` is always a non-null UUID.
'
allOf:
- $ref: '#/components/schemas/NotificationBase'
- type: object
required:
- scope
- project
properties:
scope:
type: string
enum:
- project
description: Always "project" for project-scoped notifications
project:
type: string
format: uuid
description: UUID of the project this notification belongs to (always non-null)
NotificationAccessLevel:
type: string
enum:
- admin
- viewer
description: '- `admin`: Notification visible only to project admins
- `viewer`: Notification visible to all project members
'
NotificationBulkActionResponse:
type: object
properties:
message:
type: string
description: Human-readable message describing the action taken
example: Marked 5 notifications as read
count:
type: integer
description: Number of notifications affected by the action
example: 5
Error:
type: object
properties:
error:
type: string
description: Error message
example:
error: User not found
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.
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)