Klaviyo

Search the generated catalog of every operation in Klaviyo's current stable OpenAPI revision. This reads local documentation only and does not call or change the connected Klaviyo account.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/klaviyo.catalog \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "category": "example",
    "query": "example"
  }'

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

Read the connected Klaviyo account identity, authentication mode, granted scope count, sync health, and webhook health stored for this account. By default this reads stored state only and does not call Klaviyo. Set verify=true to also make one live authenticated read against Klaviyo's accounts endpoint with the stored credential and refresh the cached account identity and status first — the same check as the app's 'Verify account now' button, useful right after rotating the API key. Either way, no secret or token value is returned and nothing in Klaviyo is modified.

Parameters

Example

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

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

Delete the system webhook from the connected Klaviyo account. New Klaviyo events will stop entering this account's automations; events already received and existing data remain stored.

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

No parameters — POST an empty body.

Example

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

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

Create a signed system webhook in the connected Klaviyo account and subscribe it to the selected live account event topics. Real customer messaging and commerce activity will begin flowing into this account's automations; this does not send messages or charge customers, but Klaviyo Webhooks API eligibility is required.

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/klaviyo.enable_webhook \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

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

List bounded, tenant-scoped Klaviyo JSON:API resources mirrored into this account for browsing and automations. This may return protected customer or marketing data but does not call or change Klaviyo.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/klaviyo.list_mirrored_resources \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "resource_type": "example",
    "limit": 50
  }'

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

List signed Klaviyo webhook deliveries and their processing state for this account. Payload bodies are omitted because they may contain message content and profile data. This does not call or change Klaviyo.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/klaviyo.list_webhook_events \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "topic": "example",
    "limit": 50
  }'

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

Run any GET endpoint under Klaviyo's fixed a.klaviyo.com /api or /client origin using this account's encrypted credential. This can read customer profiles, consent, events, campaigns, flows, reports, catalogs, custom objects, reviews, and other protected account data but does not modify Klaviyo.

Parameters

Example

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

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

Advance queued or interrupted Klaviyo synchronization jobs by one resumable batch. This may create missing contacts here but does not overwrite existing contacts or modify Klaviyo.

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

No parameters — POST an empty body.

Example

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

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

Start a resumable import of Klaviyo profiles, consent, predictive analytics, events, audiences, campaigns, flows, forms, templates, catalogs, coupons, custom objects, reviews, tags, tracking settings, and webhooks. It creates missing contacts here without overwriting existing contacts and does not modify Klaviyo.

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/klaviyo.start_sync \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

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

Run any official Klaviyo POST, PUT, PATCH, or DELETE endpoint under the fixed Klaviyo API origin. Depending on the path, this can create or delete profiles and custom objects, change consent, schedule campaigns, send messages or template previews to real recipients, publish flows, or alter live account data; provider charges may apply.

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/klaviyo.write \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "POST",
    "path": "example"
  }'

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