Iterable

REST API at api.iterable.com/api. Resources: users, events, email, sms, push, campaigns, lists, templates. POST /api/users/update creates or updates a user profile by email. POST /api/events/track records a custom event for a user (triggers journeys). GET /api/users/getByEmail retrieves a user's profile and subscription status. POST /api/email/target sends a triggered email via a specific template to a user. POST /api/lists/subscribe adds users to a list. POST /api/campaigns/metrics returns campaign performance stats. Request/response payloads are JSON. Bulk operations: POST /api/users/bulkUpdate for batch profile updates.

Standard HTTP status codes with JSON error bodies: code (integer), message (string). 401 for invalid API key, 429 for rate limit (with Retry-After). POST /api/events/track returns 200 with {status: 'success'} or error. User not found on update: creates a new user profile (upsert behavior). Campaign targeting errors (invalid template, unsubscribed user) return descriptive error messages. Iterable platform uptime at status.iterable.com. Webhook support for event delivery notifications (journey step completions, email events).

Iterable combines a CDP and a multi-channel campaign platform — user events flow in, campaigns and journeys are triggered out. For agents, the most useful patterns are: updating user profile fields (POST /api/users/update), tracking custom events that trigger journey workflows (POST /api/events/track), triggering transactional email/SMS/push sends (POST /api/email/target, /sms/target, /push/target), and managing lists (subscribe/unsubscribe). The journeys (visual workflow builder) can be triggered programmatically via custom events. Well-suited for agents orchestrating user communications in response to application events. Confidence is docs-derived.

API key auth: Api_Key {key} header. API keys from Iterable project settings → API Keys. Keys can be Standard (full read/write) or Publishable (client-side, limited to event tracking only). Project-scoped; multiple keys per project for environment separation. HTTPS enforced. Rate limits documented per endpoint group (event tracking: higher; user updates: lower). Token rotation via project settings.

api.iterable.com/api/docs provides the full interactive API reference (Swagger UI) with all endpoints, request/response schemas, and examples. Getting started requires an Iterable account (demo/trial available). API key creation straightforward. Journey + event trigger integration patterns documented in Iterable's developer guide. SDKs: mobile SDKs (iOS/Android) for in-app + push; no official server-side SDK (community-maintained Python wrapper exists). Support via Iterable support portal.