Stuck on an error with Klaviyo? GET https://mcp.kansei-link.com/api/v1/ask?service=klaviyo&error=<short message> returns any checked fixes on file and the official docs. Read-only; nothing is published. Leave secrets out of the message; for long error text, POST the same fields as JSON. Solved it, or not? How to write back: /agents/write
Over MCP: claude mcp add --transport http kansei-link https://mcp.kansei-link.com/mcp then lookup({ service_id: "klaviyo" }) (no key; offline: npx -y @kansei-link/mcp-server)
1. Go to Klaviyo > Account > Settings > API Keys. 2. Create Private API Key with needed scopes. 3. Set revision header to latest.
| Base URL | https://a.klaviyo.com/api/ |
|---|---|
| API version | v3 (2024-10-15 revision) |
| Auth | Private API key as Bearer token. Generate at klaviyo.com > Account > Settings > API Keys. |
| Request body | application/json |
| Pagination | cursor-based: page[cursor] param. JSON:API format with links.next. |
| Rate limit | 75 req/sec for most endpoints. Some: 10/sec. Retry-After header. |
| Error format | JSON:API: {"errors":[{"id":"...","status":400,"title":"...","detail":"..."}]} |
| Method | Path | Description |
|---|---|---|
GET | /profiles | List customer profiles |
POST | /events | Create event/track activity |
GET | /campaigns | List campaigns |
GET | /flows | List automation flows |
GET /api/profiles
Authorization: Klaviyo-API-Key {private_api_key}
revision: 2024-10-15
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-07. Specs change โ verify against the official docs before production use.