AdTech Integration Guide
Offers Pages will be maintained in Contentful
The Offers Pages and their individual offers will be created and maintained in Contentful by the Oddschecker Content/MarOps team. As a partner, you consume these pages through our API — no content management is required on your side.
Creating an API Key
To access the Offers Delivery API endpoints you will need an API key. Reach out to your account representative at [email protected] to obtain one.
Your API key is secret and must not be shared with external parties or users. Always ensure your code does not inadvertently expose it. If you believe your key has been compromised, contact your account representative immediately to have it rotated.
Expected Data Flow
There are two ways to integrate depending on your use case: consuming the raw JSON offers data, or embedding a pre-rendered HTML widget.
When using the raw JSON approach, do not forward API responses directly to your users. Your API key may appear in response metadata. Always handle responses server-side and serve only the data your users need.
Option 1 — Consume Raw JSON (Offers Delivery API)
Step 1: Discover Available Pages
Call GET /v1/offers/pages to retrieve the list of page paths available for your API key.
GET https://api.fairplaytechnologies.com/adtech/v1/offers/pages
api-key: <your-api-key>
Example response:
{
"pages": [
{ "page": "OC US - Bonus Bets", "path": "bonus-bets" },
{ "page": "OC - US - Sportsbook Deposit Match Bonuses", "path": "bonus-bets/deposit-match" },
{ "page": "OC US - Bonus Bets - No deposit offers", "path": "bonus-bets/no-deposit-offers" },
{ "page": "OC US - Super Bowl", "path": "bonus-bets/super-bowl" },
{ "page": "OC US - Kentucky Bonus Bets", "path": "bonus-bets/ky" },
{ "page": "OC US - New York Bonus Bets", "path": "bonus-bets/ny" },
{ "page": "OC US - Michigan Bonus Bets", "path": "bonus-bets/mi" },
{ "page": "OC US - Casino Michigan Bonus Bets", "path": "casino/mi" },
{ "page": "OC US - Casino PA Bonus Bets", "path": "casino/pa" }
]
}
Step 2: Fetch a Page
Call GET /v1/offers/pages/{path} with one of the returned paths. Use the geo headers to filter offers for a specific user location and device.
GET https://api.fairplaytechnologies.com/adtech/v1/offers/pages/bonus-bets/nc
api-key: <your-api-key>
country-code: us
subdivision-code: nc
device-type: mobile
The response contains the full OffersPage object including offers, metadata, column headers, bookie trust data, and presentation configuration. See the API reference for the full schema.
Option 2 — Embed Pre-Rendered HTML (CX Web)
For partners who want a drop-in widget without building their own UI, CX Web returns a fully rendered HTML fragment that can be embedded directly into your page.
Parameters
| Parameter | Location | Required | Description |
|---|---|---|---|
apiKey | Query | Yes | Your API key |
path | Query | Yes | The offers page path (e.g. free-bets/free-bet-no-deposit) |
countryCode | Query | No | ISO 3166-1 alpha-2 country code to geo-target offers (e.g. GB) |
subdivisionCode | Query | No | ISO 3166-2 subdivision code to further filter offers (e.g. GB-ENG) |
deviceType | Query | No | Device type to filter offers by: desktop, tablet, or mobile |
Example Request
GET https://api.fairplaytechnologies.com/adtech/v1/render/offers-page?apiKey=<your-api-key>&path=free-bets/free-bet-no-deposit&countryCode=GB&subdivisionCode=GB-ENG&deviceType=desktop
The response is a self-contained HTML fragment including linked stylesheets, the offers list, bookie trust badges, and evergreen content. Embed it directly in a <div> on your page.
The rendered HTML includes pre-bundled CSS from cx-resources.oddschecker.com. Ensure your Content Security Policy allows stylesheets and images from *.oddschecker.com and *.ctfassets.net.