Skip to content

docs(provisioning): Clarify personal_api_key is now optional for most partners#17341

Open
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-06-06T17-30-38-426Z-s7dsrr
Open

docs(provisioning): Clarify personal_api_key is now optional for most partners#17341
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-06-06T17-30-38-426Z-s7dsrr

Conversation

@inkeep
Copy link
Copy Markdown
Contributor

@inkeep inkeep Bot commented Jun 6, 2026

Changes

Updates the Provisioning API documentation to reflect that the personal_api_key response field is now optional and only returned for grandfathered partner applications.

What changed

Following PostHog/posthog#61760, PAT minting is now gated off by default for new partner applications:

  • New provisioning_issues_personal_api_key flag controls whether a partner app receives a personal API key during provisioning
  • Most apps should use the OAuth access token for API access instead
  • Only grandfathered partner apps (like the legacy Stripe integration) continue to receive a personal_api_key

Documentation updates

  1. Step 3 response – Removed personal_api_key from the JSON example since most apps won't receive it
  2. Response fields table – Clarified that personal_api_key is only returned for apps with personal API key issuance enabled
  3. Rotate credentials – Updated to note that personal_api_key is conditional
  4. Full example code – Added comment indicating personalApiKey may be undefined

This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

Reflects PR #61760 which gates PAT minting off by default.
The personal_api_key response field is now only returned for
partner apps with personal API key issuance explicitly enabled.
@inkeep inkeep Bot requested a review from MattBro June 6, 2026 17:32
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 6, 2026

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Jun 06, 2026 05:43PM

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 6, 2026

Vale prose linter → found 0 errors, 16 warnings, 11 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/integrate/provisioning.mdx — 0 errors, 16 warnings, 11 suggestions
Line Severity Message Rule
8:140 warning 'OAuth' is a possible misspelling. PostHogBase.Spelling
14:15 warning 'OAuth' is a possible misspelling. PostHogBase.Spelling
42:71 warning Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. PostHogBase.ProductNames
42:76 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
99:144 warning 'org's' is a possible misspelling. PostHogBase.Spelling
125:5 warning Capitalize 'Endpoints' for PostHog's product. Use 'endpoints' for the general industry concept. PostHogBase.ProductNames
131:50 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
131:145 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
174:59 warning 'OAuth' is a possible misspelling. PostHogBase.Spelling
190:1 suggestion Address the reader directly. Use 'you' instead of 'The user'. PostHogDocs.DirectAddress
204:42 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
271:44 warning 'OAuth' is a possible misspelling. PostHogBase.Spelling
328:183 warning 'OAuth' is a possible misspelling. PostHogBase.Spelling
332:228 warning Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. PostHogBase.ProductNames
332:233 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
344:224 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
362:199 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
424:34 warning Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. PostHogBase.ProductNames
425:34 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
436:9 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
438:35 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
441:32 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
448:14 warning Capitalize 'Endpoints' for PostHog's product. Use 'endpoints' for the general industry concept. PostHogBase.ProductNames
460:38 warning 'OAuth' is a possible misspelling. PostHogBase.Spelling
485:18 warning Capitalize 'Endpoints' for PostHog's product. Use 'endpoints' for the general industry concept. PostHogBase.ProductNames
499:20 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
611:74 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 6, 2026

Hey @MattBro! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.

  1. Review and approve the PR
  2. Merge the PR
    a. Check the preview env and CI build and merge it yourself
    b. Enable auto-merge if you're confident in the changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants