Public API Overview
Read-only REST API for querying your Trasys project's traces, logs, incidents, alerts, and sessions programmatically using your existing SDK API key today.
The Trasys Public API gives you read access to all the data your project collects — traces, logs, incidents, and alert history — using the same SDK API key you already have.
Endpoints at a glance
| Method | Path | Description |
|---|---|---|
GET | /v1/traces | Distributed traces |
GET | /v1/logs | Application logs |
GET | /v1/incidents | Incident history |
GET | /v1/alerts | Alert fire/resolve events |
GET | /v1/status-pages | Status pages |
GET | /v1/sessions | User sessions |
POST | /v1/tql | Custom TQL query |
All endpoints are scoped to your API Key. The API key automatically determines which organization and project's data is accessed.
Response envelope
All list endpoints return the same envelope:
{
"data": [ { "id": "...", "..." : "..." } ],
"meta": {
"page": 1,
"limit": 50,
"hasMore": false
}
}Errors always return a JSON object with an error key:
{ "error": "Unauthorized" }Explore
SDK Error Reference
Every error the Trasys SDK throws at startup — MISSING_KEY, INVALID_KEY_FORMAT, ENV_MISMATCH, KEY_REVOKED, and ACCOUNT_SUSPENDED — with the exact fix for each.
Authentication
Authenticate Trasys Public API requests using an X-API-Key header generated in the dashboard, plus the 401 and 403 errors returned for invalid API keys.