Members

Archive an access product so it can no longer be granted or chosen. Existing grants and any pages already gated on it keep working; archived just hides it from the pickers.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/members.archive_product \
  -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 members_archive_product at https://app.chirply.io/api/mcp, same bearer token, same input.

Create an access product — a named unit of access (e.g. 'Gold Course') you can gate pages behind and grant to members. Creating it grants no one anything on its own.

Parameters

Example

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

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

Fetch one site member by id, with the CRM contact it's linked to.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/members.get \
  -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 members_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Grant a contact an access product, unlocking every page gated on it. Idempotent — re-granting a revoked one turns it back on. Identify the person by contact_id or by member email.

Parameters

Example

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

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

Create a member (login) account for an email address, linking or creating the CRM contact behind it. Optionally email them a sign-in link right now — that sends a REAL email from the account's own email provider. Passwordless: they set no password unless they choose to.

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/members.invite \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "ada@example.com"
  }'

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

List the site members (end users with login access to this account's funnels/websites), newest first. Optionally filter by status or search by email. These are the tenant's own customers/leads who signed up for a members area — not platform staff accounts.

Parameters

Example

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

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

List the access products a contact currently holds (and any revoked ones), newest first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/members.list_entitlements \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "contact_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "email": "ada@example.com"
  }'

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

List this account's access products — the named units of access you gate pages behind and grant to members. Excludes archived ones unless include_archived is set.

Parameters

Example

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

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

Delete a member's login account and revoke access. The linked CRM contact is kept — only the ability to log in is removed. Cannot be undone.

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/members.remove \
  -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 members_remove at https://app.chirply.io/api/mcp, same bearer token, same input.

Revoke a contact's access product. Pages gated on it lock again immediately. Identify the person by contact_id or member email.

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/members.revoke_access \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "product_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Email an existing member a fresh passwordless sign-in code and magic link for a given funnel/site. Sends a REAL email from the account's own email provider.

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/members.send_login_link \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "ada@example.com",
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Set who can view a funnel page: 'public' (anyone), 'members' (any signed-in site member), or 'entitlement' (only members who hold a specific access product — pass product_id). A gated page shows the sign-in or no-access card instead of its content.

Parameters

Example

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

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

Enable or disable the member login area for a funnel/website. Turning it on exposes the /member sign-in routes and the Members management for that site; it does not by itself gate any page (use members.set_page_access for that).

Parameters

Example

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

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

Set a member's status. 'suspended' immediately blocks new sign-ins (existing sessions stop resolving too); 'active' restores access. Reversible.

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/members.set_status \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "status": "active"
  }'

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

Revoke all of a member's active sessions, forcing them to sign in again on every device. Does not delete the account.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/members.sign_out \
  -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 members_sign_out at https://app.chirply.io/api/mcp, same bearer token, same input.