Perform a lookup request
Sends details about a specific bid request to MediaGuard, then returns HUMAN’s analysis of whether the bid request is a form of invalid traffic (IVT).
Content type
The /lookup
endpoint supports body encoding in both JSON and protobuf. You can use the Content-Type
header to specify which type you’re using.
Authentication
To authenticate a request, provide an Authorization
header with the value Basic base64(username:password)
. For example, if your HUMAN Auth ID is whiteops
and your HUMAN Auth Key is secret
, your Authorization
header should be set to Basic d2hpdGVvcHM6c2VjcmV0
.
Request
The IP address of the device where the ad impression (and HUMAN’s detection tag) is intended to be delivered. This parameter expects the raw byte representation of the input address and accepts both IPv4 and IPv6 addresses.
The full URL of the site of the bid request.
Note that you must include either the url
or appID
parameter with each lookup request, but do not need to include both.
A unique identifier that HUMAN uses to identify the user driving each bid request.
For bid request in mobile environments, you should set this parameter’s value to the device’s iOS IDFA or Android AAID (when possible); for all other environments, you should generate a unique identifier that persists across all of that user’s bid request until that user’s cookies are cleared.
A string-encoded representation of the bid request’s OpenRTB supplyChainObject
.
Response
Successful lookup request that returns HUMAN’s “bot or not” decision:
A Boolean value that, when true, indicates that HUMAN has identified the bid request as invalid traffic (IVT).