Kno2 · Rate Limits

Kno2 Rate Limits

Kno2 does not publish fixed numeric rate limits for the Communication API. As a partner/enterprise, per-subscription API, throughput and any throttling are governed by the subscription agreement rather than a public per-minute cap. Kno2's own reference client consumes inbound messages by polling GET /api/messages on a loop with a 10-second wait between empty polls, which implies clients are expected to poll on a modest cadence rather than hammer the endpoint. All values here are modeled - confirm concrete limits with Kno2 during onboarding.

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

It captures 3 rate-limit definitions, measuring requests and source-ip.

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

Tagged areas include Healthcare Interoperability, Direct Secure Messaging, FHIR, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Healthcare InteroperabilityDirect Secure MessagingFHIRRate LimitingQuotas

Limits

Communication API Requests subscription
requests
not published
No fixed numeric request-rate limit is documented; governed per subscription agreement.
Intake Polling subscription
requests
client-paced (~10s interval in reference client)
The reference client polls GET /api/messages and waits 10 seconds between empty polls.
IP Allowlist subscription
source-ip
allowlisted only
Calls are rejected unless the caller's public IP is allowlisted by a Kno2 admin.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Polling Cadence
Intake/receive is client-initiated polling; poll on a modest interval rather than continuously.
Transport Security
TLS 1.2 or higher is required for all integrations.

Sources