Skip to main content
POST
Bulk invite users to project

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

Body

application/json
emails
string<email>[]
required

Email addresses to invite

Maximum array length: 100
permissions
enum<string>[]
required

Permissions granted to every invited user

  • 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
Example:
profile
enum<string>
default:contributor

Profile assigned to every invited user. Defaults to contributor when omitted.

Available options:
tech,
contributor,
user

Response

Per-email outcomes (returned even when some or all emails were skipped)

results
object[]

Per-email outcomes, in request order after deduplication

invited_new
integer
added_existing
integer
skipped
integer