Iframe Parameters

All widget configuration is passed via query parameters on the iframe src URL. Parameters fall into these categories: theme, language, odds & currency, geolocation, live scores, filters (chips and pass-through), entity scoping, date filters, hit-rate / probability thresholds, betting-market identifiers, operator filters, and display toggles.

Most non-theme parameters are forwarded to the backend /v1/trends/mixed-flows endpoint to pre-filter the feed before the first paint. See the API reference for the corresponding request body fields.

Basic Embed

<iframe
  src="https://widget.example.com/?preset=brand_dark_v2"
  width="100%"
  height="480"
  frameborder="0"
  style="border: none;"
></iframe>

Theme Parameters

Control the visual appearance of the widget.

When both colorMode and layoutMode are present alongside preset, the widget first tries a mode-specific preset file named {preset}_{layoutMode}_{colorMode}.json (e.g. brand_feed_dark.json) and falls back to the bare {preset}.json if it doesn't exist. See Presets for details.

<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&bg=1e293b"
  width="100%"
  height="480"
  frameborder="0"
  style="border: none;"
></iframe>

Language

Supported values:

<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&lang=it-IT"
  ...
></iframe>

Priority: ?lang= query param overrides the default language configured for your deployment. Falls back to en-US.

Locale matching is tolerant: values are normalized (pt_br → pt-BR), and granular regional variants resolve to the closest supported language (es-419, es-MX → Spanish). Any other value falls back to English.

Odds & Currency Parameters

Override the odds format and currency set by the preset. These take precedence over preset values.

Supported oddsFormat values:

The probability format computes implied probability from decimal odds: (1 / decimalOdds) × 100. This is useful for prediction market integrations.

The multiplier format is identical to decimal odds with an x suffix appended; it is the default for DFS product mode. The format is purely presentational — the underlying value in the payload is always the raw decimal number.

Product Mode

Supported values: sportsbook, dfs, prediction_market.

The product mode is independent of the widget mode (operator / affiliate / clean). It controls what the card looks like, not what happens on tap. See the Product Modes guide for the full breakdown.

When productMode=dfs, the API automatically scopes the feed to player over/under props (betting_market_entity_type=player, position IDs [4, 5]), defaults the odds format to multiplier, and returns stat lines with the direction prefix stripped and the odds replaced by a MORE / LESS label.

<!-- DFS product mode: multiplier odds, player overs/unders only -->
<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&productMode=dfs"
  width="100%"
  height="480"
  frameborder="0"
  style="border: none;"
></iframe>

<!-- Prediction market style: probability odds in euros -->
<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&oddsFormat=probability&currency=EUR"
  width="100%"
  height="480"
  frameborder="0"
  style="border: none;"
></iframe>

Priority: defaults → preset → iframe params. If the preset sets oddsType: "decimal" but the iframe URL has ?oddsFormat=probability, probability wins.

Geolocation

Tell the widget where the end user is located. This drives operator offer eligibility (affiliate mode) and market availability.

<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&country=US&region=NJ"
  ...
></iframe>

Live Scores & Realtime

Realtime streaming and live scores are enabled per deployment and may not be available on your plan - check with your Odditt contact. On deployments without it, these parameters have no effect and the widget renders with its initially fetched data.

See the Live Scores & Realtime guide for what updates in realtime and how the live game-state display works.

PostMessage Target

Restrict widget events to your domain so other pages embedding your iframe cannot receive them:

<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&parentOrigin=https://mysite.com"
  ...
></iframe>

See Widget Events for the full event reference and rationale.

Filter Parameters

Pre-set the widget's initial filter state. These control which flows are fetched from the API.

<!-- Show only fact flows with singles bets, overs only -->
<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&flowType=fact&betType=singles&splitType=overs"
  width="100%"
  height="480"
  frameborder="0"
  style="border: none;"
></iframe>

How Filters Work

1. Server-side rendering - filter params are parsed from the URL and included in the initial API call, so the first page load already returns filtered data.
2. Client hydration - the filter UI reflects the iframe params immediately after hydration.
3. Subsequent fetches - pagination and user-initiated filter changes use the current filter state (seeded from iframe params).

Filter Locking

When the preset includes allowOverrideIframeFilters: false, filter categories set via iframe params are locked in the UI - they show locked chip styling and their options are disabled. Filters not set via iframe remain editable.

When allowOverrideIframeFilters: true (default), users can freely change all filters, including those initially set via iframe params.

Interaction with Presets

• Iframe filter params always take precedence over preset values.
• Presets never contain filter state - filter state is controlled exclusively by iframe params and user interaction.
• Exception: factFlowType is stored in presets but can also be set via iframe params. The iframe param wins during initial state seeding.

Entity Parameters

Narrow the widget feed to a specific event, league, sport, player, or team. All are optional and can be combined.

<!-- NFL only, scoped to a specific team -->
<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&leagueKey=nfl&teamKey=chiefs"
  width="100%"
  height="480"
  frameborder="0"
  style="border: none;"
></iframe>

Entity parameters are forwarded to the backend on every API call (both SSR and client-side). Only parameters present in the URL are included - omitted parameters have no effect. Integer parameters that cannot be parsed are silently ignored. When both an ID and a key are supplied for the same entity (e.g. leagueId and leagueKey), the ID takes precedence.

Date Filters

Restrict the feed to events starting within a date window.

<!-- Only events between April 19 and April 26, 2026 -->
<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&eventStartDateFrom=2026-04-19&eventStartDateTo=2026-04-26"
  ...
></iframe>

Hit Rate & Probability Thresholds

Filter flows by historical hit rate or implied probability of the underlying bet.

<!-- Only flows that have hit at least 70% of the time -->
<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&minHitRateThreshold=70"
  ...
></iframe>

Betting Market Identifiers

Scope the feed to specific betting-market categories, positions, or markets. IDs come from the corresponding reference endpoints.

<!-- Limit to a specific category, e.g. player props -->
<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&bettingMarketCategoryId=12&bettingMarketIds=101,102,103"
  ...
></iframe>

Operator Filters

Restrict odds (and deeplinks) to specific sportsbook operators.

<!-- Odds from DraftKings and FanDuel only -->
<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&operatorKeys=draftkings,fanduel"
  ...
></iframe>

See /v1/references/operators for the full operator catalog.

Display Toggles

Boolean flags that change which flows are returned or what extra fields are included.

<!-- Feed shows only starting-soon events, with deeplinks to DraftKings -->
<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&startingSoon=true&operatorIds=10&includeDeeplinks=true"
  ...
></iframe>

Tag Filters

Segment the feed by content or metadata tags. Resolve tag type IDs from the tag registry first - see the Segmentation & Tags guide.

<!-- Only flows tagged with content types 15 or 42 -->
<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&contentTagTypeIds=15,42"
  ...
></iframe>

Misc

URL Encoding Rules

Repeated keys (?ids=1&ids=2&ids=3) are also accepted for array types if your embedder prefers HTML-form-style encoding.

Complete Example

Combining several parameter categories in a single embed:

<iframe
  src="https://widget.example.com/?preset=brand_dark_v2&bg=1e293b&lang=it-IT&oddsFormat=probability&currency=EUR&flowType=fact&betType=singles&splitType=overs&leagueKey=nfl&bettingMarketEntityType=player&eventStartDateFrom=2026-01-01&minHitRateThreshold=70&operatorIds=10,20,30"
  width="100%"
  height="480"
  frameborder="0"
  style="border: none;"
></iframe>

This embed:

• Loads the brand_dark_v2 theme preset
• Sets the page background to #1e293b
• Displays UI labels in Italian
• Shows odds as implied probability percentages
• Uses EUR currency for betslip amounts
• Shows only fact flows with singles bets and overs
• Scopes to NFL content and the player market type
• Restricts events to those starting on or after Jan 1 2026
• Hides any flow that hasn't hit at least 70% of the time
• Limits odds to operators 10, 20, and 30

API Parameter Mapping

For reference, here is how iframe parameters map to the backend /v1/trends/mixed-flows request body:

Next Steps

• Integration Recipes - how to wire these parameters up in production (theme sync, geo, empty/error handling)
• Widget Overview - introduction and flow types
• Playground - design your theme
• Presets - preset structure and deployment
• Widget Events - handle postMessage events from the widget