Jitsu · Rate Limits

Jitsu Rate Limits

Jitsu does not publish fixed numeric request-per-second rate limits for its HTTP event ingestion API. For self-hosted (MIT) deployments, throughput is bounded only by the infrastructure you provision for the Ingest service and downstream Bulker/destinations. For Jitsu Cloud, the practical limit is the monthly active-event volume of your plan (200k on Free, 2M on Business, then metered overage); the bulk endpoint can accept on the order of tens of thousands of events in a single request. Specific per-account throttling values are not documented in a public artifact.

Jitsu Rate Limits is the machine-readable rate-limit profile for Jitsu on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring events and syncs.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Event Data, CDP, Data Pipeline, Open Source, and Rate Limiting.

4 Limits Throttle: 429
Event DataCDPData PipelineOpen SourceRate LimitingQuotasThrottling

Limits

Active Events Per Month (Cloud) account
events
plan-based (200k Free / 2M Business / custom Enterprise)
Only events that reach at least one destination count; filtered events are free.
Bulk Request Size request
events
~50,000 events per bulk HTTP request
Approximate per-request capacity for POST /api/s/bulk archive uploads.
Ingestion Throughput (Self-Hosted) deployment
events
bounded by provisioned infrastructure
No fixed limit; scale the Ingest service and destinations to your needs.
Connector Syncs account
syncs
plan-based (1/day Free / 5/month Business / unlimited Enterprise)
Applies to managed connector source syncs, not event ingestion.

Policies

Plan-Based Volume
Cloud ingestion is governed by monthly active-event volume rather than fixed RPS limits.
Filtering To Reduce Volume
Use Functions to drop unwanted events before they count as active/billable.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 / Retry-After responses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/jitsu-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.