Rate Limits and Data Retention Rate Limits and Data Retention
  1. Zype
  2. Analytics
  3. Analytics 3

Rate Limits and Data Retention

To ensure performance and stability across the platform, Zype enforces rate limits on the Analytics 3 API.

Current Rate Limits

Rate limits are enforced per Zype property (site) to help balance usage across our platform.

Default Rate Limit

  • 100 requests per minute, per Zype property

Endpoint-Specific Rate Limits

The following high-intensity endpoints are subject to stricter rate limits due to the volume and complexity of the data they return:

Endpoint Rate Limit (requests/minute/site)
v2/stream_hours 10
v3/stream_hours 10
v2/playout_hours 10
v3/playout_hours 10

What Happens If You Exceed the Limit?

If your requests exceed the defined limits, you will receive a:

429 Too Many Requests response

We recommend implementing retry logic with exponential backoff in your integration to gracefully handle rate limit errors.

Data Retention & Availability

The Analytics 3 API offers different data retention windows and data capture frequencies based on the endpoint category:

Endpoint Category Example Endpoint URL Retention Period Data Capture Frequency
Revenue https://analytics.zype.com/v3/revenue/ Up to 2 years 24-hour data capture
Platform Dynamics https://analytics.zype.com/v3/platform_dynamics/ Up to 2 years 24-hour data capture
Engagement https://analytics.zype.com/v3/engagement/ Up to 13 months (starting Jan 30th, 2025) Real-time data available

Best Practices

  • Reuse API keys where appropriate to avoid unnecessary fragmentation.

  • If you're making repeated requests for the same data, consider caching the results on your end.

Need a Higher Limit?

If your use case requires a higher request rate, contact support or your account manager to discuss your options.

Was this article helpful?

0 out of 1 found this helpful

Articles in this section