DebugBundle
API

Project Members API

List, invite, update, and remove project collaborators via the DebugBundle REST API.

Manage access for one project at a time. These endpoints require browser-session or access-token authentication and re-check access against the target project on every request.

Project member operations are also available via the CLI (debugbundle project members list/invites/invite/cancel-invite/update-role/remove --project-id <id>) and MCP tools (list_project_members, list_project_member_invites, invite_project_member, cancel_project_member_invite, update_project_member_role, remove_project_member).

List Members

GET /v1/projects/{id}/members
curl https://api.debugbundle.com/v1/projects/proj_01HABCDE.../members \
  -H "Authorization: Bearer dbundle_mem_a1b2c3d4..."

List Pending Invites

GET /v1/projects/{id}/invites
curl https://api.debugbundle.com/v1/projects/proj_01HABCDE.../invites \
  -H "Authorization: Bearer dbundle_mem_a1b2c3d4..."

Invite Collaborator

POST /v1/projects/{id}/invite
curl -X POST https://api.debugbundle.com/v1/projects/proj_01HABCDE.../invite \
  -H "Authorization: Bearer dbundle_mem_a1b2c3d4..." \
  -H "Content-Type: application/json" \
  -d '{
    "email": "carol@example.com",
    "role": "member"
  }'
FieldTypeRequiredDescription
emailstringYesEmail address for the invitation.
rolestringNoProject role to assign: admin, member or read-only viewer. Default: member.

Invitations expire after 7 days. The invited user receives an email link for /invite?token=... and must sign in with the invited email address before accepting.

Cancel Invite

DELETE /v1/projects/{id}/invites/{inviteId}
curl -X DELETE https://api.debugbundle.com/v1/projects/proj_01HABCDE.../invites/pinv_01HKLMNO... \
  -H "Authorization: Bearer dbundle_mem_a1b2c3d4..."

Update Member Role

PATCH /v1/projects/{id}/members/{userId}
curl -X PATCH https://api.debugbundle.com/v1/projects/proj_01HABCDE.../members/usr_01HFGHIJ... \
  -H "Authorization: Bearer dbundle_mem_a1b2c3d4..." \
  -H "Content-Type: application/json" \
  -d '{
    "role": "admin"
  }'

Remove Member

DELETE /v1/projects/{id}/members/{userId}
curl -X DELETE https://api.debugbundle.com/v1/projects/proj_01HABCDE.../members/usr_01HFGHIJ... \
  -H "Authorization: Bearer dbundle_mem_a1b2c3d4..."

Errors

StatusCodeDescription
400invalid_payloadMissing or invalid request body.
400invalid_project_idProject ID is malformed.
400invalid_invite_idInvite ID is malformed.
400invalid_member_idMember user ID is malformed.
403forbiddenCaller cannot manage members for this project.
403upgrade_requiredProject owner's plan does not support project sharing.
403email_verification_requiredBrowser-session caller must verify email first.
404project_not_foundProject is missing or inaccessible.
404invite_not_foundNo pending invite with this ID.
404member_not_foundNo project member with this user ID.
409member_already_existsUser already has access to this project.
409invite_already_existsA pending invite for this email already exists.

Organisation access on Business

Business adds fixed organisation Owner, Admin and Member roles. The Owner controls billing, ownership transfer and destructive account actions. An organisation Admin can administer current and future projects but cannot manage the Owner or peer organisation Admins. Members have explicit selected project grants, or a deliberately chosen all-current/future-project Member or Viewer grant. Project Admins retain project-local administration; Members retain operational actions and Viewers read only.

The strongest positive grant applies; suspension denies every grant. Removing a project grant does not remove an independent inherited grant. The People view shows those sources. Team and Business count at most 1,000 unique people across the entire account, including the Owner, suspended memberships and deduplicated pending invites. There is no per-seat charge.

The People table displays cached profile images beside emails, matching project members, with initials when no image is available. GET /v1/organizations/{id}/people?include_avatars=true optionally includes protected avatar URLs. Default responses retain their existing fields. The image endpoint /v1/organizations/{id}/people/{userId}/avatar checks current organisation administrator access and that person's retained membership before returning cached bytes. It never fetches a third-party profile image on page render. CLI people reads accept --include-avatars; ordinary MCP accepts includeAvatars: true on list_organization_people.

Organisation operations use /v1/organizations, with /{id}/people, /{id}/invites and /{id}/ownership-transfer. Ownership transfer requires the verified recipient's acceptance. Switching workspaces never rewrites an automation token's scope. Invitations are accepted only by the invited verified email address.

The same services are available through debugbundle organization and ordinary MCP tools including list_organizations, list_organization_people, invite_organization_member, update_organization_member and request_organization_ownership_transfer. See the generated API reference and MCP reference for exact schemas, continuation cursors and the complete operation list. Restricted agent/OpenAI connections do not gain these management operations.

On this page