Documentation Index
Fetch the complete documentation index at: https://docs.pandaprobe.com/llms.txt
Use this file to discover all available pages before exploring further.
The PandaProbe API provides programmatic access to traces, sessions, and evaluations. All endpoints are served over HTTPS.
Every endpoint page in this reference includes an interactive playground — you can fill in parameters and send real requests directly from the docs.
Base URL
https://api.pandaprobe.com
Authentication
PandaProbe supports two authentication methods depending on the endpoint type.
Bearer JWT (management endpoints)
Used for organization management, project management, API key management, and user profile. Send the token from your identity provider in the Authorization header:
Authorization: Bearer <token>
X-Organization-ID header to specify which organization to operate on (defaults to your first membership).
API Key (data-plane endpoints)
Used for trace ingestion, trace/session queries, and evaluations. Send your org-scoped API key via the X-API-Key header along with X-Project-Name to scope the request to a project:
X-API-Key: pp_abc123...
X-Project-Name: my-project
Bearer JWT (data-plane endpoints)
You can also use Bearer JWT for data-plane endpoints by providing X-Project-ID instead of X-Project-Name:
Authorization: Bearer <token>
X-Project-ID: 550e8400-e29b-41d4-a716-446655440000
If both Authorization: Bearer and X-API-Key are present in a request, the API key takes precedence.
Summary
| Endpoint category | Auth method | Required headers |
|---|
| Organizations, Projects, API Keys, User | Bearer JWT | Authorization: Bearer <token> |
| Traces, Sessions, Evaluations | API Key | X-API-Key, X-Project-Name |
| Traces, Sessions, Evaluations | Bearer JWT | Authorization: Bearer <token>, X-Project-ID |
PaginatedResponse wrapper:
{
"items": [...],
"total": 150,
"limit": 50,
"offset": 0
}
| Parameter | Default | Range | Description |
|---|
limit | 50 | 1–200 | Number of items per page |
offset | 0 | 0+ | Number of items to skip |
Error handling
The API returns structured JSON errors:
{
"detail": "Project not found or does not belong to your organization."
}
{
"detail": "Validation error",
"errors": [
{"field": "name", "message": "String should have at least 1 character"}
]
}
HTTP status codes
| Code | Meaning |
|---|
| 200 | Success |
| 201 | Resource created |
| 202 | Accepted (async processing) |
| 204 | Deleted (no content) |
| 400 | Bad request |
| 401 | Authentication required or invalid |
| 403 | Insufficient permissions |
| 404 | Resource not found |
| 409 | Conflict (e.g., duplicate name) |
| 422 | Validation error |
| 429 | Rate limit exceeded |
Rate limits
Certain endpoints enforce per-client rate limits:
| Endpoint | Limit |
|---|
POST /traces | 100/min |
POST /evaluations/trace-runs | 50/min |
POST /evaluations/session-runs | 50/min |
POST /evaluations/monitors/{id}/trigger | 10/min |
429 Too Many Requests with a Retry-After header.
