API
REST API authentication
Authenticate against the AEON REST API with bearer tokens, understand scopes and rate limits, and handle 401/403/429 responses correctly.
5 min read
The API base URL is https://api.aeon.cloud/v1. Every request requires an Authorization header. There are no cookies and no session state.
bashbash
curl https://api.aeon.cloud/v1/executions \ -H "Authorization: Bearer $AEON_TOKEN" \ -H "Accept: application/json"
Errors
| Status | Meaning | Action |
|---|---|---|
| 401 | Missing or invalid token | Re-issue the token |
| 403 | Token lacks the required scope | Add the scope, rotate |
| 409 | Lane already reserved | Retry with backoff or drop constraints |
| 422 | PICS/PIXIT inconsistent with the suite | Run aeon config lint |
| 429 | Rate limited | Honour Retry-After |
Rate limits
texttext
X-RateLimit-Limit: 600 X-RateLimit-Remaining: 587 X-RateLimit-Reset: 1786... (unix seconds)
noteLimits are per token, per minute. Log streaming uses a websocket and does not consume the REST budget.
Run this against a real SDR lane
The tester is a service, not a box. Push a build, reserve a lane, get a verdict.