API Reference
The Nexio API is a REST API served over HTTPS. All requests and responses use JSON.Base URL
/api/v1/.
Request Format
AllPOST requests require Content-Type: application/json and a JSON body.
Authentication
All API endpoints (except/health) require authentication via the X-API-Key header.
See Authentication for details on API key types and how to obtain them.
Response Format
All responses are JSON. Successful responses include the relevant resource fields. Error responses always include anerror object:
HTTP Status Codes
| Code | Meaning |
|---|---|
200 OK | Successful request (GET) |
202 Accepted | Request accepted and queued for processing (POST job submission) |
400 Bad Request | Malformed request or missing required fields |
401 Unauthorized | Missing or invalid API key |
403 Forbidden | API key valid but insufficient permissions |
404 Not Found | Resource not found |
422 Unprocessable Entity | Request valid but cannot be processed (e.g., unknown pool) |
429 Too Many Requests | Rate limit exceeded |
500 Internal Server Error | Unexpected server error |
Rate Limiting
Rate limits are enforced per API key. The following headers are included in every response:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed per window |
X-RateLimit-Remaining | Requests remaining in current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
429 Too Many Requests. Back off and retry after the reset time.
Versioning
API versions are specified in the URL path (/api/v1/). Breaking changes are released under a new version (/api/v2/). Non-breaking additions (new fields, new endpoints) may be added to existing versions at any time.
Health Check
200 OK with {"status":"ok"}. No authentication required. Use this to verify connectivity.
Endpoints
| Method | Path | Description |
|---|---|---|
GET | /health | Health check |
POST | /api/v1/jobs | Submit an evaluation job |
GET | /api/v1/jobs/{eval_id} | Get evaluation status and results |
