Organizations
For instructions on how to authenticate to use this endpoint, see API overview.
Endpoints
GET | |
GET | |
GET | |
GET | |
GET | |
GET | |
GET | |
GET | |
GET | |
GET | |
GET | |
GET | |
GET | |
POST | |
GET | |
PATCH | |
DELETE | |
GET | |
POST | |
GET |
List all billing products
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readQuery parameters
- include_plansbooleanDefault:
false
Response
Example request
GET /api /organizations /:organization_id /billing /productsExample response
Status 200
Retrieve billing products
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readPath parameters
- product_keystring
Query parameters
- include_plansbooleanDefault:
false
Response
Example request
GET /api /organizations /:organization_id /billing /products /:product_keyExample response
Status 200
Retrieve billing products summary
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readResponse
Example request
GET /api /organizations /:organization_id /billing /products /summaryExample response
Status 200
List all billing project
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta. Every project the organization has reported usage for, deleted ones included, so a caller knows which ids a project breakdown or a team_ids filter can name. Below full billing access the list is the projects the caller can see.
Required API key scopes
billing:readResponse
Example request
GET /api /organizations /:organization_id /billing /projectsExample response
Status 200
Retrieve billing spend summary
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readResponse
Example request
GET /api /organizations /:organization_id /billing /spendExample response
Status 200
Retrieve billing spend export
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readQuery parameters
- breakdownsstring | null
- end_datestring | null
- intervalstring | null
- start_datestring | null
- team_idsstring | null
- top_projectsinteger | null
- usage_typesstring | null
Example request
GET /api /organizations /:organization_id /billing /spend /exportExample response
Status 200
Retrieve billing spend timeseries
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readQuery parameters
- breakdownsstring | null
- cursorstring | null
- end_datestring | null
- intervalstring | null
- limitinteger | null
- start_datestring | null
- team_idsstring | null
- top_projectsinteger | null
- usage_typesstring | null
Response
Example request
GET /api /organizations /:organization_id /billing /spend /timeseriesExample response
Status 200
Retrieve billing subscription
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readResponse
Example request
GET /api /organizations /:organization_id /billing /subscriptionExample response
Status 200
Retrieve billing usage summary
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readResponse
Example request
GET /api /organizations /:organization_id /billing /usageExample response
Status 200
Retrieve billing usage export
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readQuery parameters
- breakdownsstring | null
- end_datestring | null
- intervalstring | null
- start_datestring | null
- team_idsstring | null
- top_projectsinteger | null
- usage_typesstring | null
Example request
GET /api /organizations /:organization_id /billing /usage /exportExample response
Status 200
Retrieve billing usage status
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readResponse
Example request
GET /api /organizations /:organization_id /billing /usage /statusExample response
Status 200
Retrieve billing usage timeseries
In beta: the organization billing API is behind the organization-billing-api feature flag and answers 403 without it, so ask support for access. Its shapes may change while it is in beta.
Required API key scopes
billing:readQuery parameters
- breakdownsstring | null
- cursorstring | null
- end_datestring | null
- intervalstring | null
- limitinteger | null
- start_datestring | null
- team_idsstring | null
- top_projectsinteger | null
- usage_typesstring | null
Response
Example request
GET /api /organizations /:organization_id /billing /usage /timeseriesExample response
Status 200
List all cimd verification tokens
Manage CIMD verification tokens for an organization.
A partner embeds the plaintext token in their CIMD metadata document as
verification_token inside the com.posthog object (the legacy top-level
posthog_verification_token field still works as a fallback). When PostHog fetches
the metadata, matching the token links the partner app to this organization and
grants a higher default rate limit for account provisioning.
Each token is scoped at creation to the one cimd_url it will be published at,
and verifies nowhere else. Two organizations may name the same URL; only the one
whose token is actually served there verifies, so claiming a URL cannot be used
to block a partner from verifying theirs.
The plaintext value is only available on creation; we store a hash.
Required API key scopes
organization:readQuery parameters
- limitinteger
- offsetinteger
Response
Example request
GET /api /organizations /:organization_id /cimd_verification_tokensExample response
Status 200
Create cimd verification tokens
Manage CIMD verification tokens for an organization.
A partner embeds the plaintext token in their CIMD metadata document as
verification_token inside the com.posthog object (the legacy top-level
posthog_verification_token field still works as a fallback). When PostHog fetches
the metadata, matching the token links the partner app to this organization and
grants a higher default rate limit for account provisioning.
Each token is scoped at creation to the one cimd_url it will be published at,
and verifies nowhere else. Two organizations may name the same URL; only the one
whose token is actually served there verifies, so claiming a URL cannot be used
to block a partner from verifying theirs.
The plaintext value is only available on creation; we store a hash.
Required API key scopes
organization:writeRequest parameters
- labelstring
- cimd_urlstring
Response
Example request
POST /api /organizations /:organization_id /cimd_verification_tokensExample response
Status 201
Retrieve cimd verification tokens
Manage CIMD verification tokens for an organization.
A partner embeds the plaintext token in their CIMD metadata document as
verification_token inside the com.posthog object (the legacy top-level
posthog_verification_token field still works as a fallback). When PostHog fetches
the metadata, matching the token links the partner app to this organization and
grants a higher default rate limit for account provisioning.
Each token is scoped at creation to the one cimd_url it will be published at,
and verifies nowhere else. Two organizations may name the same URL; only the one
whose token is actually served there verifies, so claiming a URL cannot be used
to block a partner from verifying theirs.
The plaintext value is only available on creation; we store a hash.
Required API key scopes
organization:readPath parameters
- idstring
Response
Example request
GET /api /organizations /:organization_id /cimd_verification_tokens /:idExample response
Status 200
Update cimd verification tokens
Manage CIMD verification tokens for an organization.
A partner embeds the plaintext token in their CIMD metadata document as
verification_token inside the com.posthog object (the legacy top-level
posthog_verification_token field still works as a fallback). When PostHog fetches
the metadata, matching the token links the partner app to this organization and
grants a higher default rate limit for account provisioning.
Each token is scoped at creation to the one cimd_url it will be published at,
and verifies nowhere else. Two organizations may name the same URL; only the one
whose token is actually served there verifies, so claiming a URL cannot be used
to block a partner from verifying theirs.
The plaintext value is only available on creation; we store a hash.
Required API key scopes
organization:writePath parameters
- idstring
Request parameters
- cimd_urlstring
Response
Example request
PATCH /api /organizations /:organization_id /cimd_verification_tokens /:idExample response
Status 200
Delete cimd verification tokens
Manage CIMD verification tokens for an organization.
A partner embeds the plaintext token in their CIMD metadata document as
verification_token inside the com.posthog object (the legacy top-level
posthog_verification_token field still works as a fallback). When PostHog fetches
the metadata, matching the token links the partner app to this organization and
grants a higher default rate limit for account provisioning.
Each token is scoped at creation to the one cimd_url it will be published at,
and verifies nowhere else. Two organizations may name the same URL; only the one
whose token is actually served there verifies, so claiming a URL cannot be used
to block a partner from verifying theirs.
The plaintext value is only available on creation; we store a hash.
Required API key scopes
organization:writePath parameters
- idstring
Example request
DELETE /api /organizations /:organization_id /cimd_verification_tokens /:idExample response
Status 204 No response body
List all cross project dashboards
Dashboards the organization owns, holding insights from one or more projects.
Required API key scopes
cross_project_dashboard:readQuery parameters
- limitinteger
- offsetinteger
Response
Example request
GET /api /organizations /:organization_id /cross_project_dashboardsExample response
Status 200
Create cross project dashboards
Dashboards the organization owns, holding insights from one or more projects.
Required API key scopes
cross_project_dashboard:writeRequest parameters
- namestring
- descriptionstringDefault:
- filters
Response
Example request
POST /api /organizations /:organization_id /cross_project_dashboardsExample response
Status 201
List all cross project dashboards tiles
Tiles on one cross-project dashboard, edited one at a time.
Writes are per tile rather than a whole-set replace, so two people editing the same dashboard cannot overwrite each other's tiles.
Required API key scopes
cross_project_dashboard:readPath parameters
- dashboard_idstring
Query parameters
- limitinteger
- offsetinteger
Response
Example request
GET /api /organizations /:organization_id /cross_project_dashboards /:dashboard_id /tiles










