Koala · Rate Limits

Koala Io Rate Limits

Koala does not publish numeric request-per-second rate limits for its collection endpoints. The documented constraints are payload-shape limits on the /batch and /accounts/batch endpoints rather than throttling thresholds: each request may carry at most 30 events, 30 identifies, and 30 page_views, every event in a request must belong to the same person, and each request must include a top-level profile_id/email (or domain/account_id for accounts) plus a User-Agent header or it may be dropped as bot traffic. The Deletion (GDPR) API caps each request at 50 emails. Business-level throttling is expressed as plan quotas (identified-visitor volume and enrichment credits) rather than per-minute request ceilings.

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

It captures 7 rate-limit definitions, measuring events, identifies, page_views, profiles, and emails.

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

Tagged areas include Buyer Intent, Ingestion, Rate Limiting, Quotas, and Throttling.

7 Limits Throttle: 429
Buyer IntentIngestionRate LimitingQuotasThrottling

Limits

Events per request request
events
30
/batch and /accounts/batch accept up to 30 events per request.
Identifies per request request
identifies
30
Up to 30 identify objects per /batch request.
Page views per request request
page_views
30
Up to 30 page_view objects per /batch request.
Same-person constraint request
profiles
1
All events/identifies in a single /batch request must belong to one person.
Emails per deletion request request
emails
50
Deletion API ignores emails beyond the first 50 in a request.
Identified visitor volume account
visitors
see plan
Gated by subscription tier rather than a per-minute request limit.
Enrichment credits account
credits
see plan
Reveal/Enrich and ZoomInfo enrichment consume plan credits.

Policies

User-Agent Required
Requests without a User-Agent header may be flagged as bots and dropped.
Idempotency
Send a message_id per event to dedupe replayed/retried deliveries.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429.

Sources