The REST API gives your code the same data you see in the app. The full reference, generated from the code as OpenAPI 3.1, is at platform.logzuno.app/docs/api (raw spec: api.json).
Base URL: https://api.logzuno.app/v1.
Authentication
Send a token in Authorization: Bearer <token>. Two kinds work:
| Credential | Where | Scopes | Acts as |
|---|---|---|---|
| Personal access token | Settings → API tokens | read, write | You, within your role in each organisation |
| Project API key | Project settings → API keys | read, admin | That one project |
GET requests need read; everything else needs write (or an admin key), except running a chart, which is a read. Each token may make 300 requests a minute.
What's available
| Area | Endpoints |
|---|---|
| You | GET /me |
| Projects | GET /projects, GET /projects/{id}, GET /projects/{id}/catalogue (events, properties, channels) |
| Events | GET /projects/{id}/events, GET /projects/{id}/events/{insert_id} |
| Users | GET /projects/{id}/users, GET /projects/{id}/users/{user_id}, GET /projects/{id}/segments |
| Charts | POST /projects/{id}/charts/run (any chart spec), GET, POST, PUT, DELETE /projects/{id}/charts |
| Ask LogZuno | POST /projects/{id}/ask |
| Dashboards | GET /projects/{id}/dashboards, GET /projects/{id}/dashboards/{id}, GET …/tiles/{tile} |
| Insights | GET /projects/{id}/insights |
| Web analytics | GET /projects/{id}/web, GET /projects/{id}/web/ai |
| Alerts | GET, POST /projects/{id}/alerts; PUT, DELETE /projects/{id}/alerts/{id}; POST …/snooze, POST …/toggle; GET /projects/{id}/destinations |
The OpenAPI reference has every parameter and response shape.
Example
curl -sS "https://api.logzuno.app/v1/projects" \
-H "Authorization: Bearer $LOGZUNO_TOKEN"