Skip to main content

Acknowledgment Status Codes

Every response from the Adstract acknowledgment endpoint carries an HTTP status code. This page explains what each code means, when it happens, and how your integration should handle it.

Quick reference​

CodeNameCategoryMeaning
200OKSuccessAcknowledgment fully processed, ad cycle complete
201CreatedSuccessAcknowledgment logged, publisher is still credited, and Adstract will recover backend-side post-processing
400Bad RequestClient errorAPI key format is invalid
401UnauthorizedClient errorNo API key was provided, or the API key is invalid
403ForbiddenClient errorAPI key revoked, platform or publisher is not active, or the ad response belongs to another platform
404Not FoundClient errorad_response_id does not exist
406Not AcceptableClient errorThe ad response was not a successful enhancement
409ConflictClient errorThe ad response was already acknowledged
5xxServer ErrorServer errorOutcome is unknown, stop Adstract services until resolved

200 OK​

The acknowledgment was received and fully processed. The ad cycle is complete. The response body includes ad_ack_id, status, and success. status is ok or no_ad_used, and success is true in both cases.

201 Created​

The acknowledgment was received and logged successfully, and the publisher will still be credited. A non-critical post-processing step encountered an issue on the Adstract side and will be resolved automatically.

No action is required from the integration. The response body includes ad_ack_id, status, and success. status is recoverable_error, and success is false.

400 Bad Request​

The X-Adstract-API-Key header value is not in a valid format.

401 Unauthorized​

This code is returned when no API key was provided, or the provided API key is invalid.

403 Forbidden​

The API key is valid, but the request is not allowed.

This usually means:

  • the API key was revoked;
  • the platform or publisher account is not active; or
  • the ad_response_id belongs to a different platform than the API key.

404 Not Found​

The ad_response_id does not exist in the Adstract system.

Verify that you are passing the exact value returned by the successful enhancement response.

406 Not Acceptable​

The provided ad_response_id does not refer to a successful enhancement.

Only successful enhancement results should be acknowledged.

409 Conflict​

This ad response has already been acknowledged. Each ad_response_id can only be acknowledged once.

Treat this as a duplicate submission issue in your integration.

5xx​

A server-side failure occurred while processing acknowledgment. The outcome is unknown, which makes this status more sensitive than a normal retry scenario.

Stop Adstract services until the issue is resolved. Earlier successful traffic remains unaffected, but you should not continue sending new acknowledgment traffic blindly.

  • 200 or 201: treat as successful acknowledgment.
  • 400, 401, 403, 404, 406, 409: treat as integration or state issues and investigate.
  • 5xx: stop Adstract traffic until the issue is resolved.

Next steps​