Logspot API Overview
The Logspot API sends events, identities, and consent into Logspot and reads analytics, revenue, company, and identity data back out.
Overview
The Logspot Public API covers both directions:
- Ingestion: track events, identify users, associate them with groups, and record consent, from the browser or your servers.
- Reads: search events, query analytics and revenue, look up companies and people, list projects, and run saved actions.
To connect an AI assistant such as Claude or ChatGPT, you don't need the API. See Connect Claude and AI Assistants (MCP).
Base URL
https://api.logspot.io/v1Authentication
Every request carries one credential. API Authentication covers where to find each one and which scopes to grant.
| Credential | Header | Use it for |
|---|---|---|
Public key (pk_) | x-logspot-pk: pk_... | Client-side ingestion. Safe to expose. |
API token (sk_) | Authorization: Bearer sk_... | Server-side ingestion and reads, limited to the scopes you grant. |
| OAuth client | Authorization: Bearer <access token> | Machine-to-machine access with short-lived tokens. |
curl https://api.logspot.io/v1/track \
-H "Content-Type: application/json" \
-H "Authorization: Bearer sk_a1b2c3d4e5f6" \
-d '{"name": "Signup Completed", "user_id": "user_123"}'Ingestion calls take no project ID: the key names the project. Reads of one project's data put it in the path, /v1/projects/{project_id}/....
Endpoint Groups
Ingestion
- Events: track and search events
- Identity and Groups: tie visitors to users and users to accounts
- Consent: record consent and privacy signals
Analytics and Revenue
- Analytics: counts, unique users, and breakdowns by property
- Revenue: metrics, attribution, cohorts, and top accounts
Accounts and People
- Companies: company metrics, profiles, and Target Accounts
- Identities: person profiles, sessions, and activity
Workspace
- Organization: projects and members
- Actions: list, create, and run saved actions
- Privacy Requests: file and track deletion and export requests