Vantaca · Rate Limits

Vantaca Rate Limits

Vantaca does not publish fixed numeric rate limits for its Standard APIs. The published OpenAPI and API FAQ describe access controls (per-customer credentials, IP whitelisting, SSL-only) but no documented per-minute or per-day request cap. For bulk reads, Vantaca recommends the optional zip=true parameter on /read/ methods, which returns a compressed data.json to reduce bandwidth when pulling company-wide data - the guidance is to batch large pulls rather than issue many small requests.

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

It captures 3 rate-limit definitions, measuring requests, bytes, and dataset.

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

Tagged areas include HOA, Community Association Management, Rate Limiting, and Quotas.

3 Limits Throttle: 429
HOACommunity Association ManagementRate LimitingQuotas

Limits

Standard API Requests credential
requests
not published
No fixed numeric request-rate limit is documented for Vantaca's Standard APIs.
Bulk Read Payload request
bytes
use zip=true for bulk
/read/ methods accept an optional zip=true param returning a compressed data.json to reduce bandwidth on company-wide pulls.
Access Scope credential
dataset
per customer grant
A credential can only reach the dataset(s) the granting Vantaca customer authorized, from whitelisted IP addresses.

Policies

IP Whitelisting
Each credential set must have one or more IP addresses associated with it; requests from other addresses are rejected.
SSL Required
All connections must be made over SSL/HTTPS.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.

Sources