feat(capture): update v1 endpoint path#60176
Merged
Merged
Conversation
Contributor
|
Reviews (1): Last reviewed commit: "reset v1 capture analytics path since we..." | Re-trigger Greptile |
jose-sequeira
approved these changes
May 27, 2026
pl
reviewed
May 27, 2026
eli-r-ph
force-pushed
the
eli.r/capture-v1-analytics-path-reset
branch
from
d2f0ecd to
0461dce
Compare
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
3 participants
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.
Problem
Since the capture v1 analytics endpoint path was decided, the team has ditched the "general" label. Let's update it before we ship.
Feedback welcome if you don't agree with the new naming scheme. If this ships, I'll make a corresponding update to the RFC and OpenAPI spec we'll be shipping with the v1 analytics endpoint release.
Changes
/i/v1/general/events//i/v1/events/analytics/☝️ this makes the new scheme
/i/v<N>/<payload>/<scope>/which makes more sense for near term (ai,replay) v1 migrations on the horizon, and if we adopt alternate capture products in the future (logsetc.)How did you test this code?
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
Publish to changelog?
Docs update
🤖 Agent context