Store your bookmaker link templates

Cost: 0 credits. Store how every bookmaker link in your racing responses should be built. A FULL replacement: send the whole document each time.

Once stored, every racing response that carries a bookmaker URL also carries a ready-made twin built through your templates: source_link beside source_url (next-to-go legs, best-odds quotes, markets), betslip_win_link / betslip_place_link beside the betslip URLs (next-to-go, changes) and betslip_link beside betslip_url (best-odds). Put the *_link value on your page. A twin is absent where there is nothing to link: the book gave no URL, or your rule for that book is "none". The *_url fields are unchanged.

The document:

• mode: what a book without its own rule gets. "source" (default) links straight to the bookmaker's URL, "template" sends it through template, "none" gives no link.
• template: your tracking link with {url} where the bookmaker's URL goes (percent-encoded), or {url_raw} to insert it unencoded. Must start https://. Required when mode is "template".
• per_bookmaker: a rule per bookmaker key (ladbrokes_au, unibet, tab, ...): a template, "source" or "none". It beats mode. An unknown key is refused, so a typo cannot silently drop a book's link.

We append nothing of our own to any link. Whether a bookmaker's affiliate programme credits a click, and whether it accepts a deep-link destination at all, is between you and that programme. Prices shown to your users still need the visible "Prices by PuntersEdge" credit your plan's licence requires (Terms 8.1 and 8.3); Platform's white-label widget is the version without it.

Takes effect on your next request. Primary key only. Step-by-step guide with curl, Python and JavaScript examples: https://puntersedge.online/developers/affiliate-links