01 · Records and state owned
Campaigns, templates, catalogs, exports, events, experiments, journeys, lists, users, reporting, and other configured Iterable resources.
Iterable
Iterable
Curated major addition platform in cross-channel lifecycle marketing with material relevance to the Marcom operating stack and a first-party developer surface.
Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Campaigns, templates, catalogs, exports, events, experiments, journeys, lists, users, reporting, and other configured Iterable resources.
03 · Actions and write paths
Optional advanced modes can create, update, archive, delete, schedule, trigger, abort, and send through the underlying Iterable APIs.
04 · Authentication and permissions
Iterable API key API-key scopes, project privileges, and three explicit gates—PII, writes, and sends—govern exposure.
05 · Monitoring, approval, and recovery
Retain the safe defaults in production. Require explicit approval for sends, campaign activation, destructive actions, and PII access. Local deployment shifts credential, upgrade, network, logging, and prompt-injection controls to the customer; sends can be real and irreversible.
06 · Gaps and implementation limits
Local deployment shifts credential, upgrade, network, logging, and prompt-injection controls to the customer; sends can be real and irreversible.
Agent access
MCP and adjacent posture
Verified first-party provider MCPIterable official open-source local MCPCurrent open-source release
Role: provider
Read scope: Campaigns, templates, catalogs, exports, events, experiments, journeys, lists, users, reporting, and other configured Iterable resources.
Write scope: Optional advanced modes can create, update, archive, delete, schedule, trigger, abort, and send through the underlying Iterable APIs.
Authentication: Iterable API key
Approval boundary: Retain the safe defaults in production. Require explicit approval for sends, campaign activation, destructive actions, and PII access.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability3
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Iterable ships these experiences.
Single-platform patterns
- Cross-channel journey and messaging cockpit
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Iterable + CRM or commerce system: lifecycle journey debugger
- Iterable + warehouse or CDP + content-production platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
MCP / agent-role validationRepresentative source
https://github.com/Iterable/mcp-server ↗Iterable publishes an official local server whose setup defaults to no PII, no writes, and no sends; advanced flags can enable broad API-backed actions.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://api.iterable.com/api/docs ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://support.iterable.com/hc/en-us/categories/360002695831-API-Documentation ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://support.iterable.com/hc/en-us/articles/205480365-Webhooks-Overview ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://iterable.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Jun 4, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.