Jebbit Rate Limits
Jebbit publishes no rate limits for the v1 REST API. The Redocly-hosted reference at developers.jebbit.com and the "API overview" article in the Experiences knowledge base both document authentication, the x-jebbit-business tenant header and resource sorting, but state no request quota, no throttling window, and no rate-limit response headers. The harvested OpenAPI declares 401/403/404/400/422 responses across all 37 operations and NO 429 response on any operation, so there is not even a spec-level exhaustion signal for an agent to bind to.
Jebbit Rate Limits is the rate-limit profile for Jebbit on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the request_limit, request_remaining, request_reset, and retry_after response headers.
The profile also includes response codes documented for throttled and note.
Tagged areas include Company, Interactive Experiences, Zero-Party Data, First-Party Data, and Marketing.
request_limitrequest_remainingrequest_resetretry_after
Limits
Sources
- https://developers.jebbit.com/
- https://support-experiences.blueconic.com/en/articles/246971-api-overview
- openapi/_original/jebbit-openapi-original.json
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.