There was an unexpected error authorizing you. Please try again.

Deals API Specification

Last updated: February 6, 2026

The Deals API streamlines operations by clarifying the high-level terms of each deal, significantly reducing manual data entry and supporting automated configuration. It further enhances visibility into Curated Deals, offering transparency not currently present in the bid stream.

Version 1.0 was in Public Comment until January 31, 2026 and Finalized on Feb 6, 2026

Access the Deals API v1 Spec (Final)

The core goals of Version 1 of the Deals API are as follows:

  • Decrease manual entry of deal information across systems by providing a way for the terms of a deal to be input and sent to the system that will deliver the deal to review and accept.
  • Describe what the selling system deal includes at a high level
  • Know which parties were involved in curating and selling the package

Future iterations may include discoverability features, bi-directional communications, or Deal proposals, revisions, or negotiations. 

What it is

  • An API that provides subscribers with static information about a given Deal that outlines the tenets of the Deal.
  • This MVP is a one-party design for the origin system to PUSH information about the deal into the receiving system(s) from the system where it was created (e.g. SSP → DSP). It also allows the same system to query the receiving system for the Deal status after initial deal send. 
  • Version 1.0 of this API does not support differential overrides

How the Deals API impacts your Workflow

Deal Workflow without the Deals API

Complex error prone Deals workflow without an API

Deal Workflow with the Deals API

What it isn’t

  • This is a separate API that is NOT included in OpenRTB Request/Response
  • Does not include real-time information contained in the bid request or determine whether or not a deal applies. Implementers are strongly encouraged to validate the conditions laid out in this deal with OpenRTB requests to ensure their expectations are being met.
  • The MVP of this API does NOT support proposals, revisions, or negotiations. It is assumed those are known to implementers a priori. 
  • The MVP is not meant to support discoverability in deal marketplaces. 

Related Resources