Team

Change what a teammate can do in this account. Promoting to owner grants full control including billing, so only an owner (or the platform team) can hand the owner role out or take it away — an admin cannot. Nobody can change their own role, and demoting the last remaining owner is refused, since an organization must always keep one.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.change_role \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "user_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "role": "owner"
  }'

Over MCP the same operation is the tool team_change_role at https://app.chirply.io/api/mcp, same bearer token, same input.

Read the feature restrictions for a team member or invitation. Null means all features allowed by their role.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.get_access \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "target": "member",
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool team_get_access at https://app.chirply.io/api/mcp, same bearer token, same input.

Read whether an existing teammate or pending invitation can access no client accounts, every current and future client account, or a selected set. This reads the parent account's assignment; separately granted direct client memberships remain independent.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.get_client_access \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "target": "member",
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool team_get_client_access at https://app.chirply.io/api/mcp, same bearer token, same input.

Get the acceptance link for a pending invitation — the “Copy link” button on the team page. Use it when the invitation email didn't arrive, or to hand someone their link over chat instead. ANYONE HOLDING THIS LINK CAN JOIN THE WORKSPACE at the invitation's role until it is accepted, expires (14 days), or is revoked with team.revoke_invite, so treat it like a password: send it to the invited person and nobody else. Reading it changes nothing and sends no email.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.get_invite_link \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "invitation_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool team_get_invite_link at https://app.chirply.io/api/mcp, same bearer token, same input.

Creates an invitation and sends a real email inviting someone to join this account as a member, an admin, or an EXTERNAL client who only ever reaches Team Chat — a real message to a real person, billed to the account's own email provider. The email contains a 14-day acceptance link; owners can only be made by changing an existing member's role. The invitation is created FIRST and always survives: if the email cannot be sent (the account has no verified sending domain, or the provider failed), the invitation still exists and stays pending, `email_sent` comes back false with the reason in `delivery_status`, and the link can be handed over with team.get_invite_link or the email retried with team.resend_invite.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.invite \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "ada@example.com"
  }'

Over MCP the same operation is the tool team_invite at https://app.chirply.io/api/mcp, same bearer token, same input.

List active client accounts belonging to this parent account, for assigning teammate access. Reads names and IDs only; grants nothing.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.list_client_accounts \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool team_list_client_accounts at https://app.chirply.io/api/mcp, same bearer token, same input.

List invitations to this account that haven't been accepted or revoked yet, including which have passed their 14-day expiry and which invite an external client limited to Team Chat (`is_external`, stored with role member and shown as "Client — chat only").

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.list_invites \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool team_list_invites at https://app.chirply.io/api/mcp, same bearer token, same input.

List everyone with access to this account — name, email, role (owner/admin/member), whether they are an external client limited to Team Chat (`is_external`; such a person is stored with role member and shown as "Client — chat only"), and when they joined. Optionally narrowed by a name/email search or a single role, and returned a page at a time, exactly as the Team screen does.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.list_members \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool team_list_members at https://app.chirply.io/api/mcp, same bearer token, same input.

Remove someone's access to this account. They lose the account immediately; their records (contacts, notes, calls) stay. Removing an owner takes an owner (or the platform team) — an admin cannot remove one — though anyone may remove themselves to leave. The last owner can never be removed.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.remove_member \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "user_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool team_remove_member at https://app.chirply.io/api/mcp, same bearer token, same input.

Sends the invitation email again for an invitation that is still pending — a real email to a real person, billed to the account's own email provider. Use it after a mail outage, or once the account has connected a verified sending domain and wants invitations created before that to actually go out. It does NOT create a new invitation and does not change the existing link, its role, or its 14-day expiry, so an invitation that was already emailed will simply be emailed a second time. If the send fails again the invitation is left untouched and still pending.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.resend_invite \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "invitation_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool team_resend_invite at https://app.chirply.io/api/mcp, same bearer token, same input.

Cancel a pending invitation so its link stops working. The person can be invited again afterwards.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.revoke_invite \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool team_revoke_invite at https://app.chirply.io/api/mcp, same bearer token, same input.

Set the features a team member may use, or the restrictions inherited when an invitation is accepted. Restricts data access and available actions; does not send an email or change the person’s role. Owners retain full access.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.set_access \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "target": "member",
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "features": [
      "projects"
    ]
  }'

Over MCP the same operation is the tool team_set_access at https://app.chirply.io/api/mcp, same bearer token, same input.

Grant or remove a teammate's access to client accounts from the parent account. All includes client accounts created later; Selected includes only the IDs supplied. A pending invitation applies on acceptance. Removing an assignment immediately removes memberships created by this setting; separately granted direct client memberships remain. Sends no email and incurs no charge.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.set_client_access \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "target": "member",
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "mode": "none"
  }'

Over MCP the same operation is the tool team_set_client_access at https://app.chirply.io/api/mcp, same bearer token, same input.

Choose whether a team member sees every record in the account or only the ones assigned to them — their own contacts, the conversations on those contacts, and the messages, calls, deals and tasks that hang off them. This is a different axis from feature access, which decides which TOOLS they can open: a narrowed member can have Contacts and Conversations and still see only their own book. Enforced by the database, not just the screens, so it applies to the API and to exports as well. An owner always sees the whole account and cannot be narrowed. Setting this to "own" does not assign anybody anything — a member with no assigned contacts will see an empty list until you assign some, which is what contacts.assign and contacts.assign_by_number are for.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/team.set_record_scope \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "membership_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "record_scope": "all"
  }'

Over MCP the same operation is the tool team_set_record_scope at https://app.chirply.io/api/mcp, same bearer token, same input.