Prismatic · Rate Limits

Prismatic Rate Limits

Documented rate limits for Prismatic's management surfaces. Prismatic's GraphQL Management API enforces a throughput ceiling (commonly observed at ~20 requests per second per authenticated principal) and pagination is cursor-based with a `first` ceiling of 100 nodes per page. Prismatic does not publish a quota-per-month or per-key request budget on its public docs; the platform-side limits below are derived from documented behavior and from response semantics.

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

It captures 5 rate-limit definitions, across the shared, scale, enterprise, and custom tiers, measuring requests_per_second, nodes_per_page, and concurrent_executions.

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

Tagged areas include Embedded iPaaS, Integrations, Workflows, Rate Limiting, and Throttling.

5 Limits Throttle: 429
Embedded iPaaSIntegrationsWorkflowsRate LimitingThrottling

Limits

GraphQL API Throughput api-key
requests_per_second · second
20
GraphQL Pagination Page Size api-key
nodes_per_page · request
100
Execution Concurrency (Scale) organization
concurrent_executions · second
standard
Execution Concurrency (Enterprise) organization
concurrent_executions · second
high
Execution Concurrency (Custom) contract
concurrent_executions · second
custom

Policies

Backoff Strategy
Clients SHOULD implement exponential backoff with jitter and honor the Retry-After header when the API returns 429.
Pagination
Use cursor-based pagination with `first` and `after`. Always include a `sortBy` to guarantee stable ordering between pages.
Fair Use
Custom-tier concurrency is contractual; sustained traffic that materially impacts shared infrastructure may still be subject to fair-use throttling.