Skip to main content
POST
Ad Request

Overview

Call the API to request an ad.
This informs LynxSSP that an ad space is available and ready to be filled.
For development or testing, please refer to our Sandbox Environment to simulate API requests without affecting production data.

Authentication

All API requests require authentication using the Lynx-Key header. See Authentication for details.

Request Headers

string
default:"f9a3c4b7e2d84f85b3a2a1e3c9f071ac"
required
Unique authentication key for your account

Query Parameters

string
default:"json"
required
Specifies the response format. Accepted values: json or xmlWhen format=xml is used, the API returns the VAST tag response in XML instead of JSON.

Request Body

string
default:"venue1234"
required
Defines which venue is doing the ad request. This should be your ID in your system.Will be returned in both JSON body and the VAST tag wrapper as an extension.
string
default:"any-screen-id"
Additional information to identify which screen in the venue is sending the ad request.Will be returned in both JSON body and the VAST tag wrapper as an extension.
integer
required
Time in the future at which you expect to show the ad in UTC epoch seconds.

Response

text
required
VAST tag to be played on the specified screen and time.
string
required
Ad Request UUID to be used for Proof of Play identifier.
integer
required
Time in the future at which the ad is no longer feasible to play in UTC epoch seconds.
string
required
The venue_id sent in the ad request.
string
The screen_id sent in the ad request.
The VAST tag includes both tracking event URLs and an impression URL.
These URLs must be triggered (fired) by your player in order for impressions and tracking events to be properly recorded on our side.

Empty Response

HTTP Status Code: 204 No Content In some scenarios, the ad request endpoint may return a successful response with no body content. This typically indicates that:
  • The request was valid and processed successfully.
  • However, there are no ads to return based on the given parameters or request context.

Example Request

This example uses sandbox credentials. For production, replace with your actual API key and venue/screen IDs.

Example Response