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, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests.
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.
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.
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/highnote-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.