Phoenix Prediction Docs

Overview

Set your look in the back office, override it per page where you need to, and see what Phoenix keeps fixed

The embed is one product that every operator runs. You dress it in your brand (logo, header, font, colors, corners, spacing, mode, the shape of the feed, the style of its charts) so it sits naturally inside your site. Its structure stays the same for everyone.

Set Your Look in the Back Office

The main path is your look: you set it once, in the back office, for sandbox and production, and every embed of your operator opens already wearing it. There is nothing to pass in the iframe URL and no flash of the default look.

  • Your Look lists what you can set, how colors are kept readable, how a change reaches players, and how a page can still override it.
  • Header is the bar at the top: Full, Slim or Hidden, the parts it carries, and where the links to Activity, Leaderboard, Portfolio and Saved go.
  • The Appearance Studio is the editor: your real embed beside the settings, on every screen and device, with compare and undo.
  • Saving, Copying and Restoring covers saving per environment, copying the sandbox look to production, and bringing back the previous one.

Set How Players Bet, and Keep Them Safe

Two more settings sit beside your look in the back office, per environment, saved, copied and restored the same way:

  • Betting Settings: the bet slip's quick-amount buttons and starting amount per currency, the price format with the formats players may switch to, and whether players may cash out an open bet. Until you save them, players see prices in cents and have no price menu.
  • Player Protection: your age mark, safer-gambling message, links and helpline, and what players read when your wallet refuses a bet.

Per-Page Overrides

A URL parameter or a Host SDK call overrides your look for one page, field by field. Use them when a page should differ from your look, when your site has its own light and dark switch, or to choose a price format for one page, whichever formats your Betting settings allow. The overrides are described on Colors and Theme, Fonts and Density, Layout and Cards, Odds and Charts, Name and Logo and Changing the Look at Runtime.

What You Can Customize

WhatIn the back officePer page
Logo, or your name, in the headerYesHost SDK setBranding (Name and Logo)
Header: Full, Slim or Hidden, its parts, and where the page links goYesNo, back office only. The launch token can hide Deposit and Account for one player (Header)
FontYesfont, fontUrl (Fonts and Density)
Brand color and second colorYesaccent, secondary (Colors and Theme)
Background tintYestint, or neutralHue and neutralChroma (Colors and Theme)
Corner roundnessYesradius (Colors and Theme)
Light or dark modeYes, as the defaultmode (Colors and Theme)
Layout and card styleYeslayout, card (Layout and Cards)
Yes and No colors, colorblind paletteYesyes, no, cb (Colors and Theme)
Spacing densityYesdensity (Fonts and Density)
Odds formatBetting settings: the default and the formats players may useodds, oddsFormat, any format (Odds and Charts)
Chart line style, fill and colorsYescurve, fill, palette (Odds and Charts)
Quick-amount buttons and starting amountBetting settingsNo (Betting Settings)
Cash out of open bets: off, whole bets, or whole or partBetting settingsNo (Betting Settings)
Safer-gambling message, links, helpline, refusal reasonsPlayer protectionNo (Player Protection)
Deposit and profile buttons, per playerNoLaunch token cfg claim (Player Buttons)
Interface and content languagesOperator settingsLaunch token (Languages)
Comments, leaderboard, top holders and activityNo, set in CurationNo (Features)

Where Each Setting Lives

Settings reach the embed through four channels, chosen by who may change them:

ChannelCarriesWho can change it
Your look, in the back officeYour logo, header, font, colors (including Yes and No), corners, spacing, default mode, layout and card style, and chart line style, fill and colors, per environmentYour Admin, in the Appearance Studio
Your Betting settings and Player protection, in the back officeQuick-amount buttons, starting amounts, price formats and cash out; your safer-gambling information and what your wallet's refusal codes mean, per environmentYour Admin, under Manage > Your operator
The iframe URL (or the Host SDK's theme option and commands)Any appearance setting, for one pageYour page, on every launch. These settings are cosmetic, so it does not matter that a visitor can read or edit them
The signed launch tokenPer-player choices, such as hiding the deposit button, in the header and elsewhereOnly your backend, because only it can sign the token
Your operator settingsDisplay name, languages, the sites allowed to embed you, currenciesYour Admin in the back office (Phoenix sets the currencies). Only the sites you list can frame the embed (see Allowed Origins)

Where two of them set the same appearance field, the later wins: your look, then the URL parameters, then Host SDK calls (see Order of Precedence).

What Phoenix Keeps Fixed

  • Structure. The pages, navigation, order ticket and charts are the same for every operator. Your look chooses between vetted layouts, card styles and header arrangements, never a free arrangement. The header can move the links to Activity, Leaderboard, Portfolio and Saved into the page, or hand them to your site's menu. You choose where the embed sits on your page and how big it is (see Sizing); Phoenix owns what is inside it.
  • Legibility. You give the embed seed colors, not a full palette. Backgrounds, surfaces, text and borders use lightness steps tested for each mode, tinted by your hue. Your brand and second colors, and your chart colors, are checked for contrast against the background, and if one would be hard to read the embed uses a legible shade of the same hue instead; the text on brand-colored buttons is chosen for contrast too. From the Yes and No colors it takes only the hue, so wins and losses always read clearly. The Appearance Studio shows the colors players actually see.
  • Money and rules. Prices, balances, fees, order limits and market rules are never appearance settings.

This keeps the embed tested and accessible for every operator, while letting it carry your brand.

A Page That Differs From Your Look

Your look already carries your colors and font, so a page passes only what differs. A page that should show an orange brand color on a cool navy surface, with compact spacing and decimal odds, whatever the look says:

https://embed.prediction.phoenixverse.io/o/acme
  ?token=JWT
  &accent=%23F97316
  &neutralHue=250
  &neutralChroma=0.02
  &density=compact
  &odds=decimal

(One line in practice; %23 is the URL-encoded #.) The same with the Host SDK:

PmmEmbed.mount({
  container: '#market',
  url: 'https://embed.prediction.phoenixverse.io/o/acme',
  token: launchToken,
  density: 'compact',
  theme: {
    accent: '#F97316',
    neutralHue: 250,
    neutralChroma: 0.02,
    oddsFormat: 'decimal',
  },
})

Leave everything out and the embed wears your saved look. With no look saved, it wears the Phoenix default: dark mode, a violet brand color and the Geist font.