Skip to content

Clarify PostHog key safety #6918

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ethanpalm merged 2 commits into from
Aug 8, 2026
Merged

Clarify PostHog key safety #6918

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
38305ed
docs: clarify PostHog API key is safe to commit
ethanpalm Aug 6, 2026
bcdbaa6
💅
ethanpalm Aug 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions integrations/analytics/posthog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,8 @@ You only need to include `apiHost` if you are self-hosting PostHog. By default,

<ParamField path="apiKey" type="string" required>
Your PostHog project API key. Must start with `phc_`.

This key is a client-side token meant to be public. It's the same key your browser sends with every analytics event. It's safe to commit to your documentation repository.
</ParamField>

<ParamField path="apiHost" type="string">
Expand Down