specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Prismatic
providerId: prismatic
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-22'
tags:
  - Embedded iPaaS
  - Integrations
  - Workflows
  - Rate Limiting
  - Throttling
description: 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.
notes:
  - Prismatic does not publish a public rate-limits page. The 20 req/s figure is repeatedly cited
    in Prismatic-authored material and is enforced via HTTP 429.
  - Pagination ceiling (`first: 100`) is published on the Pagination doc.
  - Execution concurrency is plan-bound (Scale / Enterprise / Custom) and not exposed as an HTTP
    rate header — see plans/prismatic-plans-pricing.yml.
headers:
  retryAfter: Retry-After
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - tier: shared
    name: GraphQL API Throughput
    scope: api-key
    metric: requests_per_second
    limit: 20
    burst: 40
    timeFrame: second
    applies:
      - Prismatics GraphQL API
    documentation: openapi/prismatic-graphql-api-openapi.yml
  - tier: shared
    name: GraphQL Pagination Page Size
    scope: api-key
    metric: nodes_per_page
    limit: 100
    timeFrame: request
    applies:
      - Prismatics GraphQL API
    documentation: https://prismatic.io/docs/api/pagination/
  - tier: scale
    name: Execution Concurrency (Scale)
    scope: organization
    metric: concurrent_executions
    limit: standard
    timeFrame: second
    applies:
      - Prismatic Flow Runner
    documentation: https://prismatic.io/pricing/
  - tier: enterprise
    name: Execution Concurrency (Enterprise)
    scope: organization
    metric: concurrent_executions
    limit: high
    timeFrame: second
    applies:
      - Prismatic Flow Runner
    documentation: https://prismatic.io/pricing/
  - tier: custom
    name: Execution Concurrency (Custom)
    scope: contract
    metric: concurrent_executions
    limit: custom
    timeFrame: second
    applies:
      - Prismatic Flow Runner
    documentation: https://prismatic.io/pricing/
policies:
  - name: Backoff Strategy
    description: Clients SHOULD implement exponential backoff with jitter and honor the Retry-After
      header when the API returns 429.
  - name: Pagination
    description: Use cursor-based pagination with `first` and `after`. Always include a `sortBy`
      to guarantee stable ordering between pages.
  - name: Fair Use
    description: Custom-tier concurrency is contractual; sustained traffic that materially impacts
      shared infrastructure may still be subject to fair-use throttling.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com