Matillion · Rate Limits

Matillion Rate Limits

The Data Productivity Cloud API is a control-plane API for managing projects, environments, pipelines, executions, schedules, and Agents. Matillion applies standard cloud-service throttling and returns HTTP 429 when request volume is exceeded; concurrency of actual pipeline execution is governed by the account plan (included credits and concurrent-pipeline limits) rather than by a published per-second request quota. The legacy Matillion ETL REST API runs on the customer's own instance, so its throughput is bounded by that instance's size and configuration rather than by a provider-enforced quota. Specific numeric limits are not published as a single reconciled figure.

Matillion Rate Limits is the machine-readable rate-limit profile for Matillion on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests, executions, and credits.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Data Integration, ETL, ELT, Data Pipelines, and Rate Limiting.

5 Limits Throttle: 429
Data IntegrationETLELTData PipelinesRate LimitingQuotasThrottling

Limits

DPC API Request Throttling account
requests
see provider documentation
Control-plane requests are throttled and return HTTP 429 when exceeded.
OAuth Token Issuance client
requests
see provider documentation
Client-credentials token requests are subject to standard issuance throttling; cache and reuse bearer tokens until expiry.
Concurrent Pipeline Executions account
executions
governed by plan
Number of pipelines that can run at once is bounded by the subscribed plan tier, not by a request-rate quota.
Included Monthly Credits account
credits
governed by plan
Pipeline work consumes credits from the plan allotment; exhausting credits limits further execution until overage or renewal.
Legacy ETL API (Instance-Bound) instance
requests
instance-dependent
The legacy Matillion ETL REST API runs on the customer's own VM; throughput is limited by that instance's size, not a provider quota.

Policies

Plan-Governed Concurrency
Pipeline concurrency and monthly credit inclusions rise with the Basic, Advanced, and Enterprise tiers.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and reuse cached OAuth bearer tokens until they expire.

Sources