API tutorials
Errors and troubleshooting
Interpret API failures, preserve correlation IDs, and diagnose evaluations that do not progress.
Check the HTTP status and the JSON success field for every request. Preserve the response code value when you need to investigate a specific failure.
Common problems
| Symptom | Likely cause | What to check |
|---|---|---|
| 401 Unauthorized | PAT is missing, invalid, expired, or revoked | Authorization header and PAT status |
| 400 Bad Request | A required parameter is missing or empty | evaluationId, traceId, and the method-specific response field |
| No prompts found | Evaluation ID, type, or state does not match the request | Request Tutorial values and the selected GET endpoint |
| Evaluation remains Awaiting Trigger | Responses were sent to the wrong endpoint or field | BenchDX llmResponse versus RobustDX advResponse |
| Some test cases show Error | Target dispatch or response processing failed | Process Details and the model error response |
Diagnose in a fixed order
Check transport
Record the HTTP status and confirm the request reached the correct AIDX base URL.
Check authentication
Confirm the Bearer header contains a current, unrevoked AIDX PAT.
Check evaluation identity
Compare
evaluationIdwith Request Tutorial and confirm the evaluation type matches the endpoint family.Check trace and response field
Return the original
traceIdand usellmResponsefor BenchDX oradvResponsefor RobustDX.Inspect Process Details
Locate the earliest failed trace, read its model error response, and retry or explicitly handle it when appropriate.
Record the correlation ID
The response code field identifies the server request for diagnostics. It changes per request and must not be treated as a fixed success code.