What problem does it solve?
Calling a PostHog endpoint from an external app involves several easy-to-get-wrong details: the correct URL shape, personal API key auth with the right scope, the variables payload format, and error handling for rate limits and materialised endpoints. This Skill walks through each of these so client integrations work on the first attempt.
Core Features & Use Cases
- Typed client generation: Fetches the endpoint's OpenAPI 3.0 spec and guides generation of TypeScript, Python, or Go clients using @hey-api/openapi-ts, openapi-generator-cli, or oapi-codegen.
- Auth and payload guidance: Explains the Bearer personal API key header, required endpoint:read scope, and how to shape the variables payload for HogQL versus insight breakdown endpoints.
- Error handling playbook: Maps 400/401/403/404/429/5xx responses to concrete fixes, including the rule that materialised endpoints require every declared variable.
- Use Case: A developer wants to call a monthly_active_users endpoint from a Node.js backend. The Skill retrieves the endpoint config, confirms it is materialised (so all variables are mandatory), hands over the OpenAPI spec for client generation, and provides a working sample POST request.
Quick Start
Ask the agent to help you call your PostHog endpoint from your app, for example: "Help me wire up the monthly_active_users endpoint in my Node.js backend with a typed client."