What problem does it solve?
PostHog endpoints use a forward-only versioning model where any query change auto-cuts a new version and there is no pointer flip to restore an old version. This Skill guides you through safe rollback, preview, per-version settings updates, and single-version deactivation without breaking live callers.
Core Features & Use Cases
- Rollback via Forking: Retrieve an older version's query with
endpoint-get ?version=N and create a new top version containing that query, since rollback means forking rather than flipping a pointer.
- Per-Version Settings Updates: Change
description, data_freshness_seconds, or materialisation on a specific version using the version body param in endpoint-update without cutting a new version.
- Surgical Deactivation: Disable a single version with
is_active: false scoped to one version, or take the whole endpoint offline at once.
- Use Case: You shipped a broken query as v5 last night. List versions, fetch v4's query, create v6 with that query, verify it with
endpoint-run ?version=6, then deactivate v5 so no caller hits it accidentally.
Quick Start
Ask the agent to roll back your endpoint to the query from version 3 and confirm the new version works before deactivating the broken one.