Connect a PostHog account

PruneOps needs a read-only PostHog personal API key to inventory projects and feature flags, and to read subscription spend from the billing API.

How it works

One key, read-only.

01
Personal API key

In PostHog, go to Settings → My account → Personal API keys and create a key with the read-only scopes: project:read, feature_flag:read and billing:read.

02
Instance URL

The PostHog Cloud region your organization lives in — https://eu.posthog.com or https://us.posthog.com — or your self-hosted instance URL.

03
Read-only scope

Personal API keys can be scoped at creation time — nothing PruneOps does ever needs write access.

Personal API key

Covers projects, feature flags and billing.

  1. Create the key in PostHog at Settings → My account → Personal API keys (the account's credentials tab links here too), granting it the read-only scopes below. Nothing this app does ever needs write access. billing:read feature_flag:read project:read
  2. Go to Organization → Integrations → Cloud Accounts → Add Account, pick PostHog, and paste the key.

Instance URL

The region your PostHog organization lives in.

Defaults to https://eu.posthog.com — switch to https://us.posthog.com if your organization is on the US region, or point it at your self-hosted instance. It is the web app URL, not the ingestion host.

Costs

Imported daily from the PostHog billing API.

Spend arrives as a daily, per-product time series from the PostHog billing API, with the full history re-imported on every run — it all lands in the costs dashboard under the PostHog service. Requires the billing:read scope; without it, inventory and findings still work. Invoice PDFs are not API-accessible — those stay in PostHog's billing portal.

First sync

Once the account is saved, inventory runs on the next hourly cycle — or trigger it immediately from the account's detail page. Discovered Projects and Feature Flags appear under Audit → PostHog.