feat: Standardize "project token" nomenclature#48836
Merged
rafaeelaudibert merged 2 commits intomasterfrom Feb 23, 2026
Merged
Conversation
We are calling this "project API key" in many places even though this is technically wrong. We are going to be calling this "project token" going forward to avoid both internal and external confusion. Token is meant to imply this is safe to be shared publicly as opposed to a private API key. Companion PR in the posthog/posthog.com repo is PostHog/posthog.com#15229
rafaeelaudibert
requested review from
a team,
MattBro and
fercgomes
and removed request for
a team
Contributor
|
Too many files changed for review. ( |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Contributor
|
Size Change: -362 B (0%) Total Size: 100 MB ℹ️ View Unchanged
|
Contributor
|
🎭 Playwright report · View test results →
These issues are not necessarily caused by your changes. |
We can't change this
Contributor
|
Docs from this PR will be published at posthog.com
Preview will be ready in ~10 minutes. Click Preview link above to access docs at |
andrewm4894
approved these changes
Feb 23, 2026
Member
Author
Merge activity
|
rafaeelaudibert
deleted the
rafa/standardize-on-project-token-nomeclature
branch
inkeep bot
added a commit
to PostHog/posthog.com
that referenced
this pull request
Feb 23, 2026
Aligns with PostHog/posthog#48836 which standardized terminology from "project API key" to "project token" across the codebase.
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
2 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.
We are calling this "project API key" in many places even though this is technically wrong. We are going to be calling this "project token" going forward to avoid both internal and external confusion. Token is meant to imply this is safe to be shared publicly as opposed to a private API key.
Companion PR in the posthog/posthog.com repo is PostHog/posthog.com#15229
It's wise to ship this ASAP to fix the onboarding mismatch between the old and new
ph_project_tokenkeys