Base URL
https://msadsnetwork.com
Endpoints and integration notes for demand partners and publishers connecting to MS Ads Network.
Demand partners connect to the MS Ads SSP over OpenRTB 2.6. This page lists the auction endpoint, the publisher tag and what we expect from a partner integration.
https://msadsnetwork.com
Send bid requests to the SSP auction endpoint. Responses follow OpenRTB conventions.
POST /openrtb/v2/bid
Use the Method 1 SDK tag from your ad unit page for responsive, fill-aware delivery.
<script async src="https://msadsnetwork.com/msads-sdk.v2.js?client=UNIT_CODE&v=2.1.0"></script>
Demand partners receive OpenRTB 2.6 bid requests from the MS Ads SSP and return bids within the timeout. Supply transparency uses ads.txt, sellers.json and the SupplyChain object. App publishers integrate through the App SDK.
Send your company details, demand type and target formats through the partnership page.
We agree on endpoints, formats, timeouts and reporting.
A limited amount of traffic is sent so both sides can confirm requests, bids and notifications.
Volume is increased step by step while quality and spend are monitored.
Banner, native, video, push and pop impressions with site, device, geo and SupplyChain data.
Return price, creative markup and notification URLs. Bids below the floor are ignored.
Apps use the SDK init, ad and events endpoints with their app key.
ads.txt on publisher domains and sellers.json on msadsnetwork.com.
Apply as a partner. After review we share endpoint details, seat IDs and test parameters.
Test traffic can be arranged during integration. Ask our partner team.
OpenRTB 2.6.
Respond within the timeout, return valid creative markup, honour floors and creative policies, and fire win and billing notifications correctly. Creatives with malware, misleading content or prohibited categories are blocked.