Rate limits & errors
HTTP status codes returned by ingest.amlexia.com.
Success
| Code | Meaning |
|---|---|
200 | Batch accepted (events or traces) |
200 | /health OK |
Client errors
| Code | Meaning | What to do |
|---|---|---|
400 | Invalid JSON or schema | Fix payload shape; see Events |
401 | Invalid sdk_key | Rotate key in dashboard; check env var |
413 | Payload too large | Reduce batch size (maxBatchSize) |
429 | Rate limited | SDK retries; backoff or contact support |
Server errors
| Code | Meaning | What to do |
|---|---|---|
500 | Ingest error | Retry; check status.amlexia.com |
503 | Temporary unavailable | Retry with exponential backoff |
SDK behavior
Both @amlexiahq/node and amlexia:
- Batch events on an interval (default 5s)
- Retry failed uploads up to
maxRetries(default 5) - Flush remaining buffer on
shutdown()
Example error response
Shape may vary; typical body:
json
{
"error": "invalid_sdk_key"
}Debugging checklist
curl https://ingest.amlexia.com/health- Verify key in dashboard matches deployment env
- Send a single-event curl (see Troubleshooting)
- Email support with timestamp and project id (not the key)
