Docs / Capability guide
Demand routes, deals and curated marketplaces
Connect your buyer endpoint and configure routes and negotiated deals.
All capabilities · Related guide · Agent prompt for this capability
When to use this example
A buyer endpoint alone does not make demand available to a placement. Use this guide before a partner launch to check the route, placement connection and negotiated deal terms that determine whether a request can reach that buyer.
What the example gives you
The workspace inspector exports routes, placements and marketplaces for review. The guide then walks through deal setup and sandbox requests; the inspector itself makes no configuration changes.
Before you start
A buyer endpoint you control, a supported adapter, a sandbox placement, and agreed test prices.
Run the example
Extract the archive and follow README.md for setup, commands, and expected results. Start with workspace_inspect.py. Local tests use sample data.
Python tools accept --help. To connect to your workspace, supply the deployment URLs, credentials and resource IDs required by the tool.
Connect it to your application
Create a demand partner with a supported adapter and timeout_ms, then configure DemandRouteCreate.endpoints, media, QPS and prices as decimals on its route. Confirm the endpoint resolves and responds within its budget.
Attach routes directly to a placement or package them in a marketplace and attach that marketplace. Add deals with the correct kind, seats, domains, flight, currency and caps; associate packaged deals explicitly.
Inspect routes and marketplace discovery, then send an OpenRTB request with the agreed seat and deal ID. Compare the eligible and expired-flight cases; verify route rewrites with previewDemandRouteRewrites before saving them.
Check the result
The selected route/deal appears in diagnostics and reporting. Check that timeouts and ineligible deals return no bid. Guaranteed, preferred and private deals have different eligibility and pricing rules.