mParticle

mParticle is a customer data platform (CDP) that helps brands collect, unify, and activate customer data across mobile, web, OTT, and server sources, then forward it in real time to hundreds of analytics, marketing, and warehouse destinations. The mParticle developer platform exposes server Events, IDSync, Profile, Warehouse Sync, Calculated Attributes, Data Planning and Platform APIs that let teams ingest events, resolve identity, manage configurations, and orchestrate audiences using HTTP Basic, an HMAC request digest, and OAuth 2.0 client-credentials bearer tokens. mParticle was acquired by Rokt.

mParticle publishes 10 API contracts indexed on the APIs.io network, including Data Plan API, Data Plan Version API, Events API, and 7 more. Tagged areas include Customer Data Platform, CDP, Analytics, Identity Resolution, and Audiences.

The mParticle catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

mParticle’s developer surface includes authentication, changelog, sandbox, CLI, documentation, API reference, getting-started guide, and 43 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

59.5/100 strong ▬ flat Agent 46/100 agent ready Front door AI 3/6 light Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

3 published contracts 3 Agent Skills

Customer Data Platform CDP Analytics Identity Resolution Audiences Data Pipeline Marketing Data Event Streaming Data Governance

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Customer Relationship Management

BC-420

IdentifyLoginModify

POST /identify POST /{mpid}/modify POST /login

Information & Data Management

BC-610

Data PlanData Plan Version

POST / POST /validate POST /{plan_id}/versions

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 59.5/100 · strong

Contract Quality 11.4 / 19

Developer Ergonomics 6.3 / 15

Access Clarity 9.3 / 15

Operational Transparency 6.3 / 10

Contract Governance 2.9 / 9

Discoverability 6.7 / 8

Regulatory Posture 5.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 46/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 0 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/mparticle/"><img src="https://apis.io/badge/mparticle/card.svg" alt="mParticle on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too Ask about this →
Pagination +5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs Ask about this →
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified) Ask about this →

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Developer Ergonomics scores 42.3 — up to +11.5 composite points Ask about this →
Contract Quality scores 61.0 — up to +9.8 composite points Ask about this →
Contract Governance scores 31.8 — up to +8.2 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/mparticle/apis.yml: open an issue on github.com/api-evangelist/mparticle to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Martech and Customer Data Platforms	coverage	51.3	-	-
Data Marketplaces (data providers on cloud data platforms)	coverage	51.3	-	-
Mobile SDK Publishers (Play SDK Index, CocoaPods, ADA certification)	coverage	51.3	-	-
Official SDKs on Packagist, pub.dev and Hex	coverage	51.3	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 10

Individual APIs this provider publishes, each with its own machine-readable definition.

mParticle Profile API

REST API for retrieving unified user profiles, identities, attributes, and audience memberships at scale to personalize downstream applications.

mParticle Platform API

Management REST API used to programmatically configure mParticle inputs, outputs, filters, audiences, data plans, and workspace settings as part of a fully versioned CDP-as-code...

mParticle Warehouse Sync API

REST API for building reverse-ETL pipelines that pull data out of a customer data warehouse (connections, data models, field transformations and pipelines) and load it into mPar...

mParticle Data Plan API

Endpoints for managing Data Plans

mParticle Data Plan Version API

Endpoints for versioning Data Plans

mParticle Events API

Send your data to the mParticle platform.

mParticle Identify API

The Identify API from mParticle — 1 operation(s) for identify.

mParticle Login API

The Login API from mParticle — 1 operation(s) for login.

mParticle Logout API

The Logout API from mParticle — 1 operation(s) for logout.

mParticle Modify API

The Modify API from mParticle — 1 operation(s) for modify.

Scroll for all 10

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

mParticle Events Bulkevents API

OPEN COLLECTION

mParticle Bulkevents Events API

OPEN COLLECTION

mParticle Events API

OPEN COLLECTION

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Govern mParticle data plans

AGENT SKILL

Resolve a user identity with mParticle IDSync

AGENT SKILL

Send events to mParticle

AGENT SKILL

mParticle API pricing

Rate limits

mParticle Events API: 270 1s
mParticle Events API: 256
mParticle Events API: 128

All 14 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

mParticle Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

mParticle Rate Limits

14 limits

RATE LIMITS

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

mParticle

10 quoted statements, read from mParticle's own page on 2026-11-10.

TERMS

Compliance 1

Attestations the provider states (SOC 2, ISO 27001 and others), quoted from its own trust page. APIs.io verifies none of them.

mParticle

4 quoted statements, read from mParticle's own page on 2026-11-10.

COMPLIANCE

Eligibility 1

Who may sign up and where, quoted from its own terms.

mParticle

3 quoted statements, read from mParticle's own page on 2026-11-10.

ELIGIBILITY

Data License 1

How its data and outputs may be reused, quoted from its own terms.

mParticle

2 quoted statements, read from mParticle's own page on 2026-11-10.

LICENSE

FinOps 1

Cost, billing, and metering signals for API financial operations.

mParticle Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Mparticle Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

mParticle API Rules

47 rules · 44 error-severity 1 warn-severity 2 info-severity

SPECTRAL

OpenAPI Overlays 3

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

mParticle Dataplanning Overlay

5 actions · update · mparticle-dataplanning-openapi-original.yml

DERIVED

mParticle Events Overlay

6 actions · update · mparticle-events-openapi-original.yml

DERIVED

mParticle Identity Overlay

5 actions · update · mparticle-identity-swagger-original.yml

DERIVED

JSON Schema 3

Standalone JSON Schema definitions for this provider's data models.

Mparticle Eventsapi Bulk

0 properties

JSON SCHEMA

Mparticle Eventsapi Sample

0 properties

JSON SCHEMA

Mparticle Eventsapi

25 properties

JSON SCHEMA

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

mParticle Authentication

apiKey/http/oauth2 · 5 schemes

SECURITY

mParticle Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

mParticle Vulnerability Disclosure

security.txt · contact published

SECURITY

mParticle Trust Center

SOC 2, ISO 27001, GDPR

SECURITY

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

mParticle Agentic Access

16 operations · 12 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

Sandbox

DeveloperPortal

GettingStarted

SignUp

Login

Documentation 3

Reference material describing how the API behaves

JSONSchema

JSONSchema

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

AgentSkill

WellKnown

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conformance

Conventions

ErrorCatalog

Lifecycle

DataModel

Components

Webhooks

Scroll for all 7

Build 5

SDKs, sample code, and the tooling you integrate with

Packages

Packages

SDKs

SDKs

CLI

CLI

GitHubOrganization

GitHubOrganization

Postman

Postman

Access & Security 7

Authentication, authorization, and security posture

TrustCenter

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Compliance

DomainSecurity

Authentication

SecurityTxt

Scroll for all 7

Operate 2

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

RateLimits

RateLimits

Commercial 6

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

UsageTerms

DataLicense

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 7

Properties that don't map to a standard resource type

CapabilityMap

ParentCompany

Overlay

Overlay

Overlay

Attestations

Eligibility

Scroll for all 7

Source (apis.yml)

aid: mparticle
name: mParticle
description: mParticle is a customer data platform (CDP) that helps brands collect, unify, and activate customer data across
  mobile, web, OTT, and server sources, then forward it in real time to hundreds of analytics, marketing, and warehouse destinations.
  The mParticle developer platform exposes server Events, IDSync, Profile, Warehouse Sync, Calculated Attributes, Data Planning
  and Platform APIs that let teams ingest events, resolve identity, manage configurations, and orchestrate audiences using
  HTTP Basic, an HMAC request digest, and OAuth 2.0 client-credentials bearer tokens. mParticle was acquired by Rokt.
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: request
  trial: false
  try_now: false
  public: false
  label: Contact sales
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-08-13'
  method: searched
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/mparticle.png
tags:
- Customer Data Platform
- CDP
- Analytics
- Identity Resolution
- Audiences
- Data Pipeline
- Marketing Data
- Event Streaming
- Data Governance
tags_raw:
- Customer Data Platform
- CDP
- Analytics
- Identity Resolution
- Audience
- Data Pipeline
- Marketing Data
- Event Streaming
- Data Governance
url: https://raw.githubusercontent.com/api-evangelist/mparticle/refs/heads/main/apis.yml
created: '2026-05-11'
modified: '2026-08-13'
specificationVersion: '0.23'
apis:
- aid: mparticle:profile-api
  name: mParticle Profile API
  description: REST API for retrieving unified user profiles, identities, attributes, and audience memberships at scale to
    personalize downstream applications.
  humanURL: https://docs.mparticle.com/developers/apis/profile-api/
  baseURL: https://api.mparticle.com/userprofile/v1
  tags:
  - REST
  - Profiles
  - Attributes
  - Audiences
  properties:
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/profile-api/
- aid: mparticle:platform-api
  name: mParticle Platform API
  description: Management REST API used to programmatically configure mParticle inputs, outputs, filters, audiences, data
    plans, and workspace settings as part of a fully versioned CDP-as-code workflow. Authenticates with an OAuth 2.0 client-credentials
    bearer token from sso.auth.mparticle.com.
  humanURL: https://docs.mparticle.com/developers/apis/platform/overview/
  baseURL: https://api.mparticle.com/platform/v2
  tags:
  - REST
  - Management
  - Inputs
  - Outputs
  - Data Plans
  - Bearer Token
  properties:
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/platform/overview/
- aid: mparticle:warehouse-sync-api
  name: mParticle Warehouse Sync API
  description: REST API for building reverse-ETL pipelines that pull data out of a customer data warehouse (connections, data
    models, field transformations and pipelines) and load it into mParticle profiles and audiences. OAuth 2.0 client-credentials
    bearer auth.
  humanURL: https://docs.mparticle.com/developers/apis/warehouse-sync-api/overview/
  baseURL: https://api.mparticle.com/platform/v2
  tags:
  - REST
  - Warehouse
  - Reverse ETL
  - Pipelines
  - Bearer Token
  properties:
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/warehouse-sync-api/overview/
  - type: APIReference
    url: https://docs.mparticle.com/developers/apis/warehouse-sync-api/reference/
- aid: mparticle:mparticle-data-plan-api
  name: mParticle Data Plan API
  description: Endpoints for managing Data Plans
  humanURL: https://docs.mparticle.com/developers/apis/http/
  baseURL: https://s2s.mparticle.com/v2
  tags:
  - Data Plan
  properties:
  - type: OpenAPI
    url: openapi/mparticle-data-plan-api-openapi.yml
  - type: JSONSchema
    url: json-schema/mparticle-eventsapi-schema.json
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/http/
  - type: JSON Reference
    url: https://docs.mparticle.com/developers/apis/json-reference/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/idsync/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/dataplanning-api/
  - type: Postman
    url: https://docs.mparticle.com/downloads/dataplanning.postman_collection.json
- aid: mparticle:mparticle-data-plan-version-api
  name: mParticle Data Plan Version API
  description: Endpoints for versioning Data Plans
  humanURL: https://docs.mparticle.com/developers/apis/http/
  baseURL: https://s2s.mparticle.com/v2
  tags:
  - Data Plan Version
  properties:
  - type: OpenAPI
    url: openapi/mparticle-data-plan-version-api-openapi.yml
  - type: JSONSchema
    url: json-schema/mparticle-eventsapi-schema.json
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/http/
  - type: JSON Reference
    url: https://docs.mparticle.com/developers/apis/json-reference/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/idsync/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/dataplanning-api/
  - type: Postman
    url: https://docs.mparticle.com/downloads/dataplanning.postman_collection.json
- aid: mparticle:mparticle-events-api
  name: mParticle Events API
  description: Send your data to the mParticle platform.
  humanURL: https://docs.mparticle.com/developers/apis/http/
  baseURL: https://s2s.mparticle.com/v2
  tags:
  - Event
  tags_raw:
  - events
  properties:
  - type: OpenAPI
    url: openapi/mparticle-events-api-openapi.yml
  - type: JSONSchema
    url: json-schema/mparticle-eventsapi-schema.json
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/http/
  - type: JSON Reference
    url: https://docs.mparticle.com/developers/apis/json-reference/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/idsync/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/dataplanning-api/
  - type: Postman
    url: https://docs.mparticle.com/downloads/dataplanning.postman_collection.json
- aid: mparticle:mparticle-identify-api
  name: mParticle Identify API
  description: The Identify API from mParticle — 1 operation(s) for identify.
  humanURL: https://docs.mparticle.com/developers/apis/http/
  baseURL: https://identity.mparticle.com/v1
  baseurl_source: contract
  tags:
  - Identify
  properties:
  - type: OpenAPI
    url: openapi/mparticle-identify-api-openapi.yml
  - type: JSONSchema
    url: json-schema/mparticle-eventsapi-schema.json
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/http/
  - type: JSON Reference
    url: https://docs.mparticle.com/developers/apis/json-reference/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/idsync/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/dataplanning-api/
  - type: Postman
    url: https://docs.mparticle.com/downloads/dataplanning.postman_collection.json
- aid: mparticle:mparticle-login-api
  name: mParticle Login API
  description: The Login API from mParticle — 1 operation(s) for login.
  humanURL: https://docs.mparticle.com/developers/apis/http/
  baseURL: https://identity.mparticle.com/v1
  baseurl_source: contract
  tags:
  - Login
  properties:
  - type: OpenAPI
    url: openapi/mparticle-login-api-openapi.yml
  - type: JSONSchema
    url: json-schema/mparticle-eventsapi-schema.json
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/http/
  - type: JSON Reference
    url: https://docs.mparticle.com/developers/apis/json-reference/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/idsync/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/dataplanning-api/
  - type: Postman
    url: https://docs.mparticle.com/downloads/dataplanning.postman_collection.json
- aid: mparticle:mparticle-logout-api
  name: mParticle Logout API
  description: The Logout API from mParticle — 1 operation(s) for logout.
  humanURL: https://docs.mparticle.com/developers/apis/http/
  baseURL: https://identity.mparticle.com/v1
  baseurl_source: contract
  tags:
  - Logout
  properties:
  - type: OpenAPI
    url: openapi/mparticle-logout-api-openapi.yml
  - type: JSONSchema
    url: json-schema/mparticle-eventsapi-schema.json
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/http/
  - type: JSON Reference
    url: https://docs.mparticle.com/developers/apis/json-reference/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/idsync/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/dataplanning-api/
  - type: Postman
    url: https://docs.mparticle.com/downloads/dataplanning.postman_collection.json
- aid: mparticle:mparticle-modify-api
  name: mParticle Modify API
  description: The Modify API from mParticle — 1 operation(s) for modify.
  humanURL: https://docs.mparticle.com/developers/apis/http/
  baseURL: https://identity.mparticle.com/v1
  baseurl_source: contract
  tags:
  - Modify
  properties:
  - type: OpenAPI
    url: openapi/mparticle-modify-api-openapi.yml
  - type: JSONSchema
    url: json-schema/mparticle-eventsapi-schema.json
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/http/
  - type: JSON Reference
    url: https://docs.mparticle.com/developers/apis/json-reference/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/idsync/
  - type: Documentation
    url: https://docs.mparticle.com/developers/apis/dataplanning-api/
  - type: Postman
    url: https://docs.mparticle.com/downloads/dataplanning.postman_collection.json
common:
- type: CapabilityMap
  url: capabilities/mparticle-capability-edges.yml
  name: mParticle Business Capability Map
- type: ParentCompany
  url: https://apis.io/providers/rokt/
  name: Rokt
  x-relationship: acquired
  x-evidence: mParticle was acquired by Rokt.
- type: Overlay
  url: overlays/mparticle-events-overlay.yaml
- type: Overlay
  url: overlays/mparticle-identity-overlay.yaml
- type: Overlay
  url: overlays/mparticle-dataplanning-overlay.yaml
- type: AgenticAccess
  url: agentic-access/mparticle-agentic-access.yml
- type: TrustCenter
  url: security/mparticle-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/mparticle-vulnerability-disclosure.yml
- type: Security
  url: https://www.rokt.com/vulnerability-disclosure/
- type: Compliance
  url: https://trust.mparticle.com/
- type: DomainSecurity
  url: security/mparticle-domain-security.yml
- type: Authentication
  url: authentication/mparticle-authentication.yml
- type: Conformance
  url: conformance/mparticle-conformance.yml
- type: Conventions
  url: conventions/mparticle-conventions.yml
- type: ErrorCatalog
  url: errors/mparticle-problem-types.yml
- type: Lifecycle
  url: lifecycle/mparticle-lifecycle.yml
- type: ChangeLog
  url: changelog/mparticle-changelog.yml
- type: RateLimits
  url: rate-limits/mparticle-rate-limits.yml
- type: Plans
  url: plans/mparticle-plans-pricing.yml
- type: Sandbox
  url: sandbox/mparticle-sandbox.yml
- type: DataModel
  url: data-model/mparticle-data-model.yml
- type: Packages
  url: packages/mparticle-packages.yml
- type: SDKs
  url: packages/mparticle-packages.yml
- type: CLI
  url: cli/mparticle-cli.yml
- type: Components
  url: components/mparticle-components.yml
- type: Webhooks
  url: asyncapi/mparticle-webhooks.yml
- type: X-MCPServerCandidate
  url: mcp/mparticle-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: WellKnown
  url: well-known/mparticle-well-known.yml
- type: SecurityTxt
  url: well-known/mparticle-security.txt
- type: JSONSchema
  url: json-schema/mparticle-eventsapi-schema.json
- type: LLMsTxt
  url: llms/mparticle-llms.txt
- type: GitHubOrganization
  url: https://github.com/mparticle
- type: LinkedIn
  url: https://www.linkedin.com/company/mparticle-inc-
- type: Website
  url: https://www.mparticle.com/
- type: Documentation
  url: https://docs.mparticle.com/
- type: DeveloperPortal
  url: https://docs.mparticle.com/developers/
- type: APIReference
  url: https://docs.mparticle.com/developers/apis/http/
- type: GettingStarted
  url: https://docs.mparticle.com/guides/getting-started/
- type: Postman
  url: https://docs.mparticle.com/downloads/dataplanning.postman_collection.json
- type: Pricing
  url: https://www.mparticle.com/pricing/
- type: SignUp
  url: https://www.mparticle.com/get-a-demo/
- type: Login
  url: https://app.mparticle.com/login
- type: TermsOfService
  url: https://www.mparticle.com/legal/platform-terms-of-service/
- type: PrivacyPolicy
  url: https://www.mparticle.com/privacypolicy/
- url: https://www.mparticle.com/blog/
  type: Blog
- type: UsageTerms
  url: terms/mparticle-terms-of-service.yml
- type: Attestations
  url: compliance/mparticle-compliance.yml
- type: Eligibility
  url: eligibility/mparticle-eligibility.yml
- type: DataLicense
  url: data-license/mparticle-data-license.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 35
  pass: local-v1

mParticle API — frequently asked questions

Does mParticle have an API?

Yes. APIs.io lists 10 APIs from mParticle, including mParticle Profile API, mParticle Platform API and mParticle Warehouse Sync API, and 7 more.

Is there an OpenAPI specification for the mParticle API?

Yes. APIs.io indexes 7 OpenAPI specifications for mParticle, each linked for download from this page.

How do I authenticate with the mParticle API?

mParticle documents its authentication (apiKey/http/oauth2 · 5 schemes). The details are profiled on APIs.io as mParticle Authentication.

Is the mParticle API ready for AI agents?

mParticle has a Kin Score of 59.5 out of 100 (strong) and an Agent Readiness score of 45.7 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/mparticle"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/mparticle/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/mparticle/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.