Skip to main content
PATCH
Edit a pending invitation

Authorizations

Authorization
string
header
required

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..

Path Parameters

project_id
string<uuid>
required

UUID of the project

invite_id
string<uuid>
required

UUID of the invitation

Body

application/json
permissions
enum<string>[]
  • 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)
Available options:
CAN_PERFORM_ADMIN_ACTIONS,
CAN_VIEW_DATA,
CAN_IMPERSONATE_OTHER_USERS
profile
enum<string>
default:contributor

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
Available options:
tech,
contributor,
user

Response

Invitation updated

id
string<uuid>
email
string<email>
permissions
enum<string>[]
  • 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)
Available options:
CAN_PERFORM_ADMIN_ACTIONS,
CAN_VIEW_DATA,
CAN_IMPERSONATE_OTHER_USERS
profile
enum<string>
default:contributor

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
Available options:
tech,
contributor,
user
status
enum<string>
  • pending: Invitation sent, awaiting response
  • accepted: User accepted the invitation
  • cancelled: Invitation was cancelled
Available options:
pending,
accepted,
cancelled
created_at
string<date-time>
updated_at
string<date-time>
invited_by
object
assigned_interview_count
integer

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.