Request API: AD endpoint
The AD endpoint is used for integrations that can't parse a JSON response and require the response to be in specific markup.
GET request
The AD endpoint can only be used by using a Get request and - similar to the GET version of the JSON endpoint - slot level parameters are not supported.
The GET version of the ad request contains the same information as the POST version with one limitation:
slot level parameters are not supported.
Example request
https://ads-[account].adhese.com/ad/sl_sdk_example_-leaderboard/ctsports;soccer?t=244.18664863333106| Section | Description |
| https://ads-[account].adhese.com | The domain is either the default ads domain for your account or a configured first-party domain. More info on first-party domains can be found here. |
| /ad/ | |
| /sl[location code]-[format code]/ | This section can be added more than once. Each placement starts with the prefix 'sl', followed by the full slot code. |
|
/ctsports;soccer/ |
This section can be added more than once. Each target section starts with its predefined prefix and is followed by either one value or a list of values separated by ';'. |
|
?t=[timestamp] |
A timestamp to avoid caching issues |
Response codes
| Code | Name | Description |
|---|---|---|
200 |
OK | Body contains an array of ads. If no ads are available, the array is empty — an empty array is a successful response, not an error. |
454 |
No slots | The request body contains no slots. Header x-adhese-bad-request contains slots cannot be empty. |
500 |
Internal server error | If this was a debug request, check the debug log; otherwise contact Adhese Support. |
When handling errors programmatically, read the x-adhese-bad-request response header for the specific message.