Endpoint that DSPs must implement to receive bid requests from Thrads SSP (ssp.thrads.ai). Called by the SSP orchestrator during multi-bidder auctions.
Implementation Required: Your DSP must implement this endpoint on your own server. The SSP at ssp.thrads.ai will send POST requests to your configured DSP endpoint URL.
Conversation history. Must contain at least 2 messages (user and assistant). Messages must alternate between user and assistant roles, ending with a user message followed by an assistant message.
REQUIRED (when bidding) - Bid amount in CPM (cost per mille) dollars. Must be >= 0. Should have 2 decimal places. Values with more decimals will be rounded using banker’s rounding (IEEE 754).
Optional - Pre-rendered ad creative. When included, the SSP skips the render step entirely and serves this ad directly.Important: If ad_data is present but invalid (missing required fields, wrong types, or unknown fields), the entire bid is rejected — treated as a no-bid with reason invalid_ad_data. Only include this if you’re confident in the format.
Error message when the request fails. Only present on error responses.
Pre-rendered ad_data validation is strict. The SSP validates ad_data against the exact render response schema (extra="forbid"). Unknown fields will cause the bid to be rejected. Required fields: headline, description, url. If you include ad_data, the render endpoint (/render-ad) is never called for that bid — make sure the ad creative is complete.