Admixer HelpCenter

In cases where Bid Requests from the SSP partner do not meet the system's requirements, these Bid Requests will not be processed. Instead, they will be recorded in the statistics as Filtered HTTP Requests.

To simplify the investigation process, the system will respond with a 400 status code, indicating an Invalid Request, and will provide an appropriate No Bid Reason in the response body.

The general structure of a No Bid Reason response is as follows:

{ 
    "id": "1234567890",  // request ID; if it's impossible to get the RequestID, null is used as the default.
    "seatbid": [],       // always empty
    "nbr": 501           // nbr ID
}

NBR Codes and Their Descriptions

NBR Code	Description
501	Flags requests where the maximum response time ("tmax") is unrealistically low, potentially causing issues with bid responses. The minimum threshold is 50ms.
502	Indicates that the specified bid floor in the request exceeds the acceptable limit. The maximum threshold is $50.
503	Identifies requests with a structure that does not conform to the expected format or protocol.
504	Flags requests with an excessive number of impression objects, potentially indicating an error, misuse, or system overload.
505	Indicates that the request is missing an essential impression object.
506	Flags requests where the advertising ID ("ifa") is missing, which may impact tracking and targeting.
507	Indicates an impression opportunity with an impression ID that does not meet the specified criteria or format.
508	Flags an impression opportunity with a native ad object that does not conform to the expected structure.
509	The mandatory parameter is missing for video or audio impression objects.
510	Indicates that the request lacks the necessary user-agent information, which can affect the request processing.
511	Flags requests without the "app" or "site" object. At least one of them should be in place for valid request processing.
512	Indicates requests missing domain or bundle parameter. At least one of them should be in place for valid request processing.
513	Flags requests if there were more than 50 with the same device ID within a short time frame (60 seconds). Each subsequent request after the 50th will be filtered.
514	Flags requests with a supply chain object that does not adhere to the expected structure or values.
515	Identifies an impression opportunity with a Private Marketplace (PMP) object that does not conform to the expected structure or criteria.
516	Identifies non-human traffic, including robots, crawlers, checkers, download agents, spam harvesters, and feed readers, by analyzing the User-Agent with the assistance of a third-party device identification vendor.
517	Too many requests.
518	The "tmax" value is either missing or invalid.
519	Indicates that the IP is either missing in the request or invalid.
521	Type of the request does not match the Endpoint type.
522	The request contains both site and app data (bundle and domain), but only one environment type should be included.
523	This filter targets incoming HTTP requests associated with device IDs that are recognized as suspicious or fraudulent, based on Pixalate's Pre-bid lists.
524	This filter identifies and flags incoming HTTP requests originating from IP addresses deemed suspicious, based on Pixalate's Pre-bid lists.
525	This filter flags incoming HTTP requests with OTT devices that are known to be involved in fraudulent activity, based on Pixalate Pre-bid lists.

Updated on October 29, 2024