Trigger evaluation
Evaluation runs asynchronously. The endpoint returns immediately with202 Accepted.
Poll evaluation status
Fetch the current status and results for a version. The response includes per-file results, so single-file promotions return an array of one.status is pending and its result is absent. When a file fails, its status is failed and no result is returned. A 404 means no evaluation exists for the version yet; trigger one first.
Aggregate status:
Recommended flow
- Trigger the evaluation with
POST .../evaluate. - Receive the result via a webhook. This is the recommended approach: Adclear pushes the result to your endpoint as soon as it’s ready, with no polling.
GET .../evaluation every 5 to 10 seconds until status is succeeded or failed.
Polling example
Troubleshooting
Evaluation stuck in processing
Evaluation stuck in processing
Typical evaluation time is 30 to 90 seconds. Continue polling every 5 to 10 seconds for up to 5 minutes. If it’s still processing after that, re-trigger with
POST .../evaluate. If it persists, contact support with the correlationId and evaluationId.Evaluate returns 400, 409 or 422
Evaluate returns 400, 409 or 422
The evaluation engine rejected the version’s input, for example because its communication type is no longer available.
POST .../evaluate returns the engine’s status code, and error.message gives the engine’s reason. The error.code is CONFLICT for a 409 and INVALID_REQUEST for a 400 or 422. These errors come from the request rather than an outage, so fix the cause the message names before you trigger again.A 502 with UPSTREAM_ERROR means the engine itself was unavailable. Retry after a short delay.Can I re-evaluate the same version?
Can I re-evaluate the same version?
Yes. Each
POST .../evaluate creates a new evaluation, and GET .../evaluation always returns the most recent result for that version. Previous results are retained internally for audit.