Projects

Organizations and projects provide the workspace, tenancy, and authorization model for Lariba Cloud.

The examples on this page use human-user Bearer authentication:

Authorization: Bearer YOUR_ACCESS_TOKEN

Organization endpoints

Create an organization

POST /v1/organizations

{
  "name": "Example Organization",
  "slug": "example-organization"
}

Request fields:

Successful response:

{
  "id": "ORGANIZATION_UUID",
  "name": "Example Organization",
  "slug": "example-organization",
  "owner_id": "USER_UUID",
  "created_at": "2026-07-24T00:00:00+00:00"
}

The authenticated creator becomes the organization owner.

Organization members

Organization member responses include:

Listing, updating, and removing organization members require owner-level organization authority.

Update an organization role

PATCH /v1/organizations/{organization_id}/members/{user_id}

{
  "role": "operator"
}

Allowed roles:

• admin;
• operator;
• member;
• viewer.

The organization owner role is immutable. Attempting to change it returns a conflict response.

Remove an organization member

DELETE /v1/organizations/{organization_id}/members/{user_id}

Successful response:

{
  "message": "Organization membership removed"
}

The organization owner cannot be removed through this endpoint.

Invitations

Create an invitation

POST /v1/organizations/{organization_id}/invites

{
  "email": "operator@example.com",
  "role": "operator"
}

Request fields:

Owner invitation responses include the invitation identifier, organization identifier, sanitized target identity, requested role, status, timestamps, email-delivery result, and delivery status.

Accept an invitation

POST /v1/organizations/invites/{invite_id}/accept

The optional request body can contain an invitation token:

{
  "token": "INVITATION_TOKEN"
}

The token, when supplied, must be 10–512 characters.

Invitation audits

GET /v1/organizations/{organization_id}/invitation-audits

Optional query parameter:

Audit responses include action, outcome, reason code, requested role, request identifier, invitation identifier, and creation time.

Project endpoints

Create a project

POST /v1/projects

{
  "organization_id": "ORGANIZATION_UUID",
  "name": "Production",
  "slug": "production"
}

Request fields:

Successful response:

{
  "id": "PROJECT_UUID",
  "organization_id": "ORGANIZATION_UUID",
  "name": "Production",
  "slug": "production",
  "owner_id": "USER_UUID",
  "created_at": "2026-07-24T00:00:00+00:00"
}

Select a project

POST /v1/projects/select

{
  "project_id": "PROJECT_UUID"
}

The response uses the standard project representation.

Project members

Add a member

POST /v1/projects/{project_id}/members

{
  "user_id": "USER_UUID",
  "role": "operator"
}

user_id is required. role defaults to member.

Allowed project roles:

• owner;
• admin;
• operator;
• member;
• viewer.

Project member responses contain:

• project_id;
• user_id;
• role;
• created_at.

Organization membership remains authoritative for project access, and organization membership changes are synchronized to project memberships.

Project capabilities

GET /v1/projects/{project_id}/capabilities

{
  "project_id": "PROJECT_UUID",
  "can_read_delivery": true,
  "can_replay_delivery": true,
  "can_retry_now_delivery": true,
  "can_drain_delivery_dlq": false,
  "can_manage_delivery_channels": false
}

Capability fields describe the current user’s effective Delivery permissions. Backend authorization remains authoritative.

Project events

GET /v1/projects/{project_id}/events

Supported query parameters:

The response includes project identity, project name, total count, pagination values, effective time bounds, and event items.

Daily usage

GET /v1/projects/{project_id}/usage/daily

Query parameter:

The response contains the project identifier and an array of daily usage items.

Common responses

Related documentation

• Organizations and Projects concept
• Authentication
• API Keys
• Events API
• Usage reference