01 · Records and state owned
Accounts, workspaces, apps and services, audiences, calculated attributes, data points, feeds, field transformations, keys, users, and data plans with versions and validation schemas.
mParticle
mParticle
mParticle is included for first-party APIs that manage customer-data platform configuration, audiences, feeds, transformations, calculated attributes, users, and versioned data plans used to validate incoming event data.
Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaSReverse ETL / activation
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
Retrieve account-scoped platform configuration for workspaces, apps, audiences, attributes, data points, feeds, transformations, services, users, and versioned data plans or schemas.
03 · Actions and write paths
Create or update supported platform entities and forwarding services; create, update, delete, and version data plans; and use plan schemas to govern data quality.
04 · Authentication and permissions
Client-credentials authentication yields an approximately eight-hour bearer token. Platform requests are scoped to an account ID, while Data Planning operations also require the target workspace and corresponding API access.
05 · Monitoring, approval, and recovery
Show the account, workspace, app, feed, service, transformation, and data-plan version before changes. Keep data plans in source control and preserve review or approval before activating schemas that govern validation of incoming events.
06 · Limits and caveats
The reviewed first-party sources document APIs, not a provider MCP. Platform tokens cannot be revoked before their roughly eight-hour expiry, account ID is required for most calls, and separate mParticle API families have their own access and behavior.
First-party access
Documented surfaces
Warehouse Sync SQL models ↗mParticle Warehouse Sync defines warehouse data models for one-time, on-demand, or recurring pulls from supported warehouses. SQL executes against the connected customer warehouse, subject to connection and pipeline permissions.Source: Warehouse Sync User GuidemParticle Warehouse Sync Reverse ETL ↗mParticle explicitly describes Warehouse Sync as its Reverse ETL solution for ingesting warehouse profile or event data into mParticle. Forwarding onward uses separate output integrations, and input-protection mode governs profile changes.Source: Warehouse Sync API OverviewMCP / agent surface ↗Third-party/community MCP only; no first-party provider verifiedAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience
Agent access
MCP support
Third-party onlyCommunity MCP only; first-party status unresolved
Support: Third-party only
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.
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 access1
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that mParticle ships them.
Single-platform patterns
- Customer-data quality and audience routing console
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- mParticle + CRM or commerce system: lifecycle journey debugger
- mParticle + 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.
6 recorded sources
Platform core validationRepresentative source
https://docs.mparticle.com/developers/apis/platform/overview/ ↗Accounts, workspaces, apps, audiences, data plans and versions, data points and events, feeds, calculated attributes, transformations, services, users, warehouse syncs, and DSRs. Create and update platform entities;…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party core-access review
APISource inventory
https://docs.mparticle.com/developers/apis/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Developer docsSource inventory
https://docs.mparticle.com/developers/ ↗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.
Developer docsSource inventory
https://docs.mparticle.com/guides/data-warehouse-sync/ ↗Reverified the named access facet exactly as bounded by the reviewed first-party record.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
HomepageSource inventory
https://www.mparticle.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
mParticle Warehouse Sync Reverse ETLTargeted review
Warehouse Sync API Overview ↗mParticle explicitly describes Warehouse Sync as its Reverse ETL solution for ingesting warehouse profile or event data into mParticle. Forwarding onward uses separate output integrations, and input-protection mode…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party access review
Verified fact
Tied to cited first-party evidence reviewed for this profile.
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.