Quick Start

Integrate publisher pages with a managed, shared decision API.

Delivery model

  • Shared API endpoint: https://api.shftd2.com
  • One organization credential: X-API-Key
  • Publisher metadata per request: placement_id, optional site_id, section, brand, page_url

One integration endpoint is enough to activate delivery across your publisher properties.

Validate with one curl

curl -A "Mozilla/5.0 (compatible; GPTBot/1.0; +https://openai.com/gptbot)" \
  "https://api.shftd2.com/decision?partner_id=pub_1&placement_id=slot_01&ua_class=agent&lang=en&site_id=yourmedia_main&section=auto&brand=carco&page_url=https%3A%2F%2Fwww.yourmedia.com%2Fauto%2Farticle-123" \
  -H "X-API-Key: <YOUR_API_KEY>"

Expected result: signed decision payload is returned (or controlled 204 No ad).

Publisher parameters

  • partner_id (required): organization identifier provided by DoubleShift
  • placement_id (required): publisher slot identifier (example: slot_01)
  • ua_class (required): traffic class (human, agent, ...)
  • lang (required): request language code (example: en)
  • site_id (optional): publisher property/inventory identifier (recommended for multi-site setups)
  • section (optional): editorial context from CMS (example: auto)
  • brand (optional): campaign context label for targeting (example: carco, back_to_school)
  • page_url (optional): full publisher page URL; request URL can be used if omitted

Targeting inputs

  • Access is secured with X-API-Key.
  • site_id is an inventory context key (not an auth key).
  • Targeting uses hybrid inputs:
  • explicit metadata (site_id, section, brand) when available
  • URL-derived context from page_url when metadata is missing

This keeps integration light while preserving publisher-level targeting control.