Repository navigation
Clarify event and request size limits (1 MiB / 10 MiB) and fix 413 example - #346
Merged
Merged
Conversation
…ample - Fix /import 413 example to report the actual 10485760-byte request cap - State exact byte limits for per-event (1,048,576) and per-request (10,485,760) sizes, and note over-size events get a 400 - Add per-event size limit to the events and properties FAQ - Fix broken #rate-limits anchor on the track page Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WZEB62ivGnogwXg1JegNzt
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
 [Low impact] The documentation changes appear safe to merge. Reviews (3) · Last reviewed commit: "Merge branch 'main' into claude/event-si..." · Reviewed by Greptile |
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WZEB62ivGnogwXg1JegNzt
kurbycchua
enabled auto-merge (squash)
October 23, 2026 01:18
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Kurby Chua · Slack thread
Before: The Import Events page says
/importaccepts 10MB uncompressed per request, but the 413 example in the ingestion OpenAPI spec saysrequest exceeds max limit of 2097152 bytes(2MB). The 1MB per-event limit appeared only on the API reference pages, with no note on what happens when an event is too large, and wasn't mentioned in the events and properties FAQ. The Track Event page also linked to a nonexistent#rate-limitsanchor.After: The 413 example reports
request exceeds max limit of 10485760 bytes. The Track Event and Import Events pages keep the per-event limit as 1MB of uncompressed JSON and now note that larger events are rejected with a 400 error. The "What are the limits of events and properties?" FAQ now mentions the per-event size limit and links to the Track Event limits section. The Track Event link now points to/reference/import-events#rate-limit, matching the "Rate Limit" heading.How: Limits were confirmed against Mixpanel's ingestion code: the per-event cap is 1 MiB (1,048,576 bytes) of raw JSON after gzip decompression (400 on
/trackand/import), and the/importrequest cap is 2000 events and 10 MiB (10,485,760 bytes) measured after decompression (413). The encoder's internal 2 MiB record cap is not customer-facing, which is where the old 2097152 example came from.2097152appeared nowhere else in the repo.🤖 Generated with Claude Code
https://claude.ai/code/session_01WZEB62ivGnogwXg1JegNzt