Validic · Rate Limits

Validic Rate Limits

Validic's Inform REST API applies a default rate limit of 2,000 requests per access token per hour. Data-retrieval requests are additionally bounded by a maximum date range of 30 days per request; up to 1 year of data is available via the API (7 years are retained for compliance). The Streaming API is capped at 5 streams per customer with up to 3 concurrent client connections per stream, and emits a poke (heartbeat) event every 5 seconds to keep the connection alive.

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

It captures 5 rate-limit definitions, measuring requests, days, streams, and connections.

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

Tagged areas include Health Data, Digital Health, Rate Limiting, and Quotas.

5 Limits Throttle: 429
Health DataDigital HealthRate LimitingQuotas

Limits

Inform REST API Requests token
requests
2000 per hour
Default limit of 2,000 requests per access token per hour.
Data Query Date Range request
days
30 per request
A single data-retrieval request may span at most 30 days.
Data Availability Window account
days
365 via API
Up to 1 year of data is retrievable via the API; 7 years retained for compliance.
Streams Per Customer account
streams
5
A customer may create up to 5 streams.
Concurrent Stream Connections stream
connections
3
Events are distributed across up to 3 concurrent client connections per stream.

Policies

Heartbeat
The Streaming API sends a poke event every 5 seconds over the SSE connection to keep it alive.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Date-Range Paging
Retrieve long histories by paging the 30-day maximum window across successive requests.

Sources