GrowthZone · Rate Limits

Growthzone Rate Limits

GrowthZone does not publish fixed numeric rate limits for its REST API in the public integration documentation. The API is per-customer-database and gated behind an issued API Key, so throughput is governed operationally per account rather than by an advertised per-minute request cap. Read endpoints are paged (responses carry TotalRecordAvailable and a Results array) and callers are expected to page rather than pull everything at once. For bulk synchronization, GrowthZone provides a delta feed (GET /api/contacts/delta) so integrations can fetch only changed records instead of repeatedly scanning the full dataset.

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

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

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

Tagged areas include Association Management, AMS, Membership Management, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Association ManagementAMSMembership ManagementRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the GrowthZone REST API.
Result Paging endpoint
records
paged
List endpoints return TotalRecordAvailable plus a paged Results array; page through large sets.
Delta Sync account
requests
recommended
Use GET /api/contacts/delta to sync only changed contacts instead of polling full lists.

Policies

API Key Required
Every request must send Authorization; ApiKey {API_Key}. Keys are issued per application and can be revoked.
Pagination
Prefer paged reads and reasonable page sizes over unbounded pulls of the full database.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources