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, in the API Commons Rate Limits shape.

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

Limit state is signalled in the retryAfter response header, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429 retryAfter
Method: generated, dated 2026-05-22.
Written by API Evangelist on 2026-05-22 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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.

Work with this as data

Every rate limit 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 rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • 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 rate limit 
curl "https://apis.io/api/v1/rate-limits/prismatic-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.