Highnote Rate Limits
Highnote applies per-account rate limiting to the single GraphQL endpoint to protect platform stability. The documentation describes rate limiting as a resilience consideration and recommends idempotency keys and retry-with-backoff, but does not publish specific numeric request-per-second or request-per-minute thresholds. Specific limits are not reconciled in this artifact.
Highnote Rate Limits is the machine-readable rate-limit profile for Highnote on the APIs.io network, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring requests.
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.
Tagged areas include Card Issuing, Embedded Finance, Fintech, Payments, and GraphQL.
generated, dated 2026-06-20.
Limits
Policies
Sources
- https://docs.highnote.com/docs/developers/api/using-the-api
- https://docs.highnote.com/docs/developers/api/intro-to-graphql
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.