Pismo · Rate Limits

Pismo Rate Limits

Pismo is a cloud-native, horizontally-scaled platform. Public documentation describes OAuth2 access tokens that expire after one hour (3600 seconds) and account-specific tokens for account-scoped calls, but does not publish specific per-endpoint request-per-second or per-minute quotas. Throughput, burst, and concurrency limits are governed by the client's commercial agreement and environment (sandbox vs. production). Specific values are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests, concurrent_requests, seconds, and tokens.

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

Tagged areas include Banking, Card Issuing, Payments, Fintech, and Core Banking.

4 Limits Throttle: 429
BankingCard IssuingPaymentsFintechCore BankingCloud NativeRate LimitingQuotasThrottling

Limits

Requests Per Second (RPS) client
requests
see provider documentation
Per-environment throughput governed by commercial agreement; not publicly published.
Concurrency client
concurrent_requests
see provider documentation
Concurrent request ceilings vary by environment and contract.
Access Token TTL client
seconds
3600
OAuth2 client-credentials access tokens expire after one hour and cannot be renewed; request a new token.
Account Token account
tokens
account-scoped
Account-specific endpoints require an access token encoded with a Pismo account ID.

Policies

Token Expiry
Access tokens are valid for 3600 seconds; clients must request a fresh token on expiry.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Environment Separation
Sandbox (sandbox.pismolabs.io) and production (api.pismo.io) enforce separate limits and credentials.

Sources