The API Report CardAPI Index
Matillion

Matillion API

matillion.com

Two documented public REST APIs cover the product line: the Data Productivity Cloud API and the legacy Matillion ETL v0/v1 API, each with its own auth and conventions. Access rides on a Matillion license. Docs are mid-migration into the Maia hub and links break.

Last verified: October 2026Software & Data ToolsMCP READY
API GRADE
C
VERIFIED OCT 2026

SCORECARD

ExistenceGOODTwo documented REST APIs ship: the Data Productivity Cloud API and the legacy Matillion ETL v0 and v1 instance API.
AccessMIXEDCredentials come from your DPC hub or ETL instance; access rides on a Matillion license, not a public developer signup.
CoverageMIXEDProjects, environments, schedules, and pipeline runs are covered; the thin webhook surface pushes integrators to polling.
AuthMIXEDOAuth 2.0 and bearer tokens on the DPC API, HTTP Basic on legacy ETL instances; two conventions to maintain.
Docs & DXPOORDPC API docs are mid-migration into the Maia hub, breaking long-standing links; integrators juggle two doc sets.
StabilityMIXEDLegacy ETL caps at 60 requests per minute, so bursty pollers hit 429s; Oct 2025 pipeline incidents ran most of a day.
MCPGOODMatillion publishes an official MCP server for the Data Productivity Cloud API as the npm package @matillion/mcp-server, updated in July 2026. Official docs cover authentication and client setup and the server exposes over 60 tools for pipelines, schedules, and environments. docs.maia.ai ↗ VERIFIED 2026-08
MORE FROM THE REPORT CARD
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Matillion scores C on Supergood's API Report Card. Two documented public REST APIs cover the product line: the Data Productivity Cloud API and the legacy Matillion ETL v0/v1 API, each with its own auth and conventions. Access rides on a Matillion license. Docs are mid-migration into the Maia hub and links break.

Tried to integrate with Matillion?
SOURCES
Two parallel API surfaces (Matillion ETL v0/v1 vs Data Productivity Cloud) with different auth, pathing, and payload conventions force integrators to learn both docs.matillion.com ↗
DPC API documentation is in flux and now redirects into the Maia docs hub, breaking long-standing links docs.matillion.com ↗
Rate limits (60 req/min on Matillion ETL) are low for orchestrators that poll job status aggressively; 429s are common during burst windows docs.matillion.com ↗
Limited webhook surface, most integrations end up polling /run and /status endpoints rather than receiving push notifications docs.matillion.com ↗
Custom Connector framework (RSD/API Profiles) is powerful but has a steep authoring learning curve; community reports of friction integrating new partner APIs documentation.matillion.com ↗
Pipeline Execution incidents in both US and EU regions on Oct 15, 2025 caused job failures; variable validation and transformation errors took most of the day to resolve status.matillion.com ↗
Maia AI service was unavailable in the EU region on Oct 13, 2025, errors, timeouts, no-response failures across AI-assisted pipeline authoring status.matillion.com ↗
StatusGator tracked 8 Matillion incidents (3 major outages, 5 minor) with a median 1h56m duration in a recent 90-day window statusgator.com ↗
Behavior and entitlements differ between DPC (SaaS) and Matillion ETL (instance), integrations built against one can require rework when a customer migrates docs.matillion.com ↗
Credit consumption is opaque at runtime, task-hour billing across many concurrent pipeline runs is difficult to attribute back to individual API calls or jobs without dedicated monitoring matillion.com ↗
Credit-based pricing is unpredictable; reports of $12K–$24K annual baselines escalating significantly via credit overages improvado.io ↗
Customers buying 12 seats end up with only 3 active users, license waste tied to learning curve and concurrent-user limits g2.com ↗
Steep learning curve between 'simple ETL' and 'production-grade pipelines', reports of 6+ weeks to onboard a new data engineer integrate.io ↗
Cloud (Data Productivity Cloud) version still missing capabilities the older server-based Matillion ETL product offers trustradius.com ↗
Phone support effectively unavailable; email support response times measured in days g2.com ↗
Persistent OOM (out-of-memory) errors on large jobs; one reviewer reported recurring monthly OOMs after a year of tuning and doubled instance size g2.com ↗
UI autosaves bad inputs and lacks undo for some destructive actions; debugging large pipelines is time-consuming g2.com ↗
Connector count (~150) trails Fivetran and Airbyte; customers regularly fall back on the Custom Connector framework airbyte.com ↗
Multiple recent platform incidents, Pipeline Execution degradation in US and EU on Oct 15, 2025; Maia AI unavailable in EU on Oct 13, 2025; 8 incidents in a recent 90-day window per StatusGator status.matillion.com ↗
Concurrent-developer limits in shared environments create bottlenecks for larger data engineering teams integrate.io ↗