June · Rate Limits

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, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring tracking_events, embed_api_requests, and data_deletion_requests.

The profile also includes response codes documented for throttled and success.

Tagged areas include Analytics, Product Analytics, B2B SaaS, Event Tracking, and Segment Compatible.

3 Limits Throttle: 429
AnalyticsProduct AnalyticsB2B SaaSEvent TrackingSegment CompatibleRetentionFeature AdoptionActivation

Limits

workspace
tracking_events · per_minute
unspecified
workspace
embed_api_requests · per_minute
unspecified
workspace
data_deletion_requests · per_day
unspecified