Background: We're experiencing intermittent 400 BAD REQUEST errors when bulk publishing cooking classes through the Eventbrite API. We typically need to publish multiple events simultaneously (scheduling classes in bulk).
Current Issue: The publish endpoint (https://www.eventbrite.com/platform/api#/reference/event/publish/publish-an-event) has specific rate limits that are separate from the general API rate limits:
The Problem: Our application monitors the x-rate-limit response headers to dynamically throttle requests and stay within API limits. However, these publish-specific rate limits are NOT reflected in the standard x-rate-limit headers, creating a blind spot where we can be within general API limits but still hit publish-specific thresholds. We were told by our account manager these are managed by the Trust & Safety team and she has yet to get more details from them.
What We Need:
We're willing to implement proper throttling logic if we can get visibility into these publish-specific limits.
Additional Context:
Has anyone else encountered this issue or found a solution for monitoring publish-specific rate limits?