June Rate Limits
June does not publicly document specific rate limit thresholds for its Tracking API or other endpoints. The API uses HTTP 429 status codes for throttling when limits are exceeded. Consumers should implement exponential backoff and use the Retry-After header when present. Rate limits may vary by plan tier and MAU count.
June Rate Limits is the machine-readable rate-limit profile for June on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions, measuring tracking_events, embed_api_requests, and data_deletion_requests.
Limit state is signalled in the retryAfter and retryAfterHeader response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes response codes documented for throttled and success.
Tagged areas include Analytics, Product Analytics, B2B SaaS, Event Tracking, and Segment Compatible.
retryAfterretryAfterHeader
generated, dated 2026-06-12.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.