Brand configuration
The brand is the group code of your merchants (the brand from GET /v1/merchant). It holds the sportsbook look and rules, the same for every currency in the group. The TALOS team configures it in the back office; ask your contact for changes.
What can be configured#
Appearance#
- Theme — one of the ready-made themes as a base, plus the brand colors (accent, backgrounds, texts, odds, live, success/error), corner radius, a Google Fonts font and per-component tweaks (odds buttons, betslip, tabs, header, banner, mobile navigation, etc.).
- Layout — one of the ready-made layouts (
sidebar,classic,tile) or a custom structure: which blocks appear on each page (banner, sports carousel, live highlights, ready-made parlays, featured leagues, sports tree), in which order and on which screen sizes.
Betslip and bets#
- Quick stakes of the betslip, minimum bet and step, per currency.
- Maximum selections per betslip and per system bet.
- Quick bet (one tap on the odds) on or off.
- Allowed odds formats and the default one (decimal, fractional, American).
- Default odds change acceptance: never, only higher or any.
The brand can only tighten the sportsbook limits (higher minimum bet, fewer selections), never loosen them.
Content and navigation#
- Features: banner, ready-made parlays, favorites, search, my bets.
- Sports: hide sports and set the priority order.
- Regions: countries pinned at the top of the navigation (after the player's country).
- Banner and call-to-action texts in Portuguese, Spanish and English.
How your site interacts#
- Nothing besides the
brand_idneeds to be sent in the SDK: theme, layout, texts and rules come from the brand. themeNameandlayoutin the SDK override the brand only on that page (useful for A/B tests or special pages). Without them, the brand applies.- Changes are published in versions; once published they reach players within 1 minute (cache).
- TALOS can show a preview before publishing and roll back to a previous version.
Note
If your group code changes, the brand configuration follows it. Update the SDK brand_id (or always read it from GET /v1/merchant).