Highnote · Rate Limits

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.

2 Limits Throttle: 429
Card IssuingEmbedded FinanceFintechPaymentsGraphQLRate LimitingQuotasThrottling

Limits

GraphQL Requests account
requests
see provider documentation
Per-account rate limiting on the single GraphQL endpoint; exact thresholds not published.
Mutating Operations account
requests
see provider documentation
Use idempotency keys so retried mutations do not double-execute.

Policies

Idempotency
Supply an idempotency key on mutations so safe retries do not duplicate side effects.
Backoff Strategy
Implement exponential backoff with jitter and honor 429 responses / Retry-After.
Pagination
Use Relay cursor connections (first / after) to page large result sets rather than large single requests.

Sources