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: JPMorgan Chase
providerId: jp-morgan-chase
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-05'
reconciled: false
notes: JPMorgan Chase does not publish a single canonical rate-limit table for its developer
  APIs. Limits are documented per product inside the J.P. Morgan Developer Portal and are
  governed by the client agreement. Reconciliation blocked pending portal-level rate-limit
  documentation.
tags:
  - Banking
  - Financial Services
  - Payments
  - Treasury
  - Rate Limiting
description: Rate-limit artifact for JPMorgan Chase Payments / Treasury / Embedded Banking
  APIs. No public per-second / per-minute number is canonical; limits are enforced per
  product and per client.
sources:
  - https://developer.payments.jpmorgan.com/
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Per-product, per-client throttle
    scope: client/product
    metric: varies
    limit: see J.P. Morgan Developer Portal product documentation
policies:
  - name: Backoff Strategy
    description: Clients should implement exponential backoff with jitter on 429 / 503 responses
      and honor the Retry-After header when present.
  - name: Idempotency
    description: Payment-class endpoints (ACH, Wires, RTP, card auth) require idempotency
      keys; safe retry depends on idempotency-key reuse.
  - name: Client-Provisioned Limits
    description: Steady-state and burst limits are configured per client per product;
      raises and whitelist changes go through the J.P. Morgan implementation team.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com