Base URL
All API endpoints are versioned under/v1:
Authentication
Pikarc supports two authentication mechanisms:API Key (SDK endpoints)
Used by the SDK for machine-to-machine communication. Pass the key as a Bearer token:lg_<prefix>_<secret>
- The
prefixis used for fast database lookup - The
secretis verified against a SHA256 hash - Keys are generated on registration and can be regenerated in the dashboard
JWT Token (Dashboard endpoints)
Used by the web dashboard. Obtained via the login endpoint:Endpoint Auth Requirements
| Auth Type | Used For | Endpoints |
|---|---|---|
| API Key only | SDK write operations | POST /v1/runs/, step creation, step updates |
| JWT or API Key | Dashboard + SDK read | Run listing, workspace config, usage, API keys |
| JWT only | User account operations | /v1/auth/me, billing, password change |
| None | Public | /v1/auth/login, /v1/auth/register, /health |
Error Responses
All errors return a JSON body with adetail field:
Status Codes
| Code | Meaning |
|---|---|
400 | Bad request — invalid input |
401 | Unauthorized — missing or invalid auth |
403 | Forbidden — feature not available on your plan |
404 | Not found |
422 | Validation error — invalid request body |
500 | Internal server error |
Plan-Gated 403 Errors
Some operations are restricted by plan tier. For example, enabling the kill switch on a Basic or Pro plan returns:Health Check
200 OK with the API status. No authentication required.