MS Ads Network Alliance
Docs

Partner documentation pack

Technical overview for Alliance supply and demand partners. Secrets and production endpoints are issued after approval — nothing sensitive is published here.

1. OpenRTB connection

We support a direct OpenRTB connection between MS Ads Network and your stack (you call our endpoint, or we bid into yours — agreed per partner).

  • Authentication: API key issued per partner seat.
  • Network lock: Partner IP addresses are allowlisted; requests from unknown IPs are rejected.
  • Protocol: OpenRTB-compatible bid request / bid response JSON.
  • Geos: Enabled markets are listed in your partner agreement (for example US, CA, NG when agreed).

We do not publish live API keys, endpoint URLs with credentials, or sample secrets on this site.

2. ads.txt / sellers.json / schain

Buyers must be able to verify the supply path.

  • Publish correct ads.txt lines on every domain that monetises through the Alliance.
  • Maintain an accurate sellers.json if you resell or operate as an intermediary.
  • Pass a complete SupplyChain object (schain) when you are not the first seller.

MS Ads Network public files:

Exact ads.txt / sellers.json lines for your seat are confirmed when the test is set up.

3. Integration checklist

  1. Apply via Join and await approval email from partner@msadsnetwork.com.
  2. Confirm OpenRTB direction, sample bid request/response shape, and partner IPs.
  3. Receive API key + seat configuration (offline / partner pack).
  4. Add ads.txt / sellers.json / schain declarations on test domains.
  5. Run a non-exclusive test on agreed geos and formats.
  6. Review quality and commercial terms before scaling.

4. Standards

Clean traffic only. No bots, no incentivised clicks, no adult / gambling / crypto or other restricted categories on either side. Read our open standards: https://standards.msadsnetwork.com.