Multipliers, salaries and prices are three different numbers

A single schema with one numeric column called value is the fastest way to corrupt this data. The three datasets each carry a number attached to a player or a game, and those numbers answer different questions. Joining them is fine. Comparing them directly is where products start saying things the data cannot support.

Three numbers at a glance

Pick6 multipliers

The standings_multiplier field is a nullable number on each selection, and formatted_standings_multiplier is a separate nullable label. Keep both. In the November 3, 2026 snapshot none of the 12,294 stored selections had a null multiplier, but the contract allows it, so your schema should too. A sample without nulls is not a promise about tomorrow.

Selections are also not always in pairs. In the same snapshot, 10,042 of 11,168 market rows carried a single explicit selection and 1,126 carried two or more. Every explicit source selection is retained, even when one-sided. Do not synthesize a missing side or assume the two sides are symmetrical.

Sportsbook prices

As of 2026-11-03, native sportsbook scopes cover New York NFL, NHL, college basketball and college football game lines and New York NHL Shots on Goal, points, assists, saves, goalscorers, power-play points and first-period shots. Read snapshots and streamed changes through the sportsbook endpoints. ESPN-attributed DraftKings moneyline, spread and total observations are also available across eight leagues. Current scope inventory is listed at /api/v1/sportsbook/scopes.

A moneyline has a price and no handicap line. Spread records keep explicit signed source lines, and totals keep the source total. Read event_status before you read a price. It is pre, in, post or unknown, and a quotation from a completed game is history. Source price update time remains null, so the capture time is the only clock you have.

DFS salaries

One athlete can have multiple roster-slot draftables, so deduplicating by athlete can discard valid salary choices. Key on the draftable record instead. DFS salaries and FPPG are not sportsbook lines, and redistribution remains permission-gated, which is why a DFS request can return 403.

A schema that keeps them apart

CREATE TABLE pick6_selection (
  pick_group_id text NOT NULL,
  pickable_id text NOT NULL,
  pickable_market_id text NOT NULL,
  side text,                 -- unknown stays NULL
  standings_multiplier numeric, -- NULL is not zero
  observed_at timestamptz NOT NULL
);

CREATE TABLE sportsbook_price (
  offer_id text PRIMARY KEY,
  event_id text NOT NULL,
  market text NOT NULL,
  american integer,
  line numeric,
  observed_at timestamptz NOT NULL
);

CREATE TABLE dfs_draftable (
  draftable_id text PRIMARY KEY,
  slate_id text NOT NULL,
  salary integer,
  observed_at timestamptz NOT NULL
);

Separate tables make the wrong comparison awkward, and awkward is what you want here. If you do put these numbers on one screen, label each with its meaning and its capture time.

Wording to avoid in your product

• Do not call a standings multiplier odds, a payout or a price.
• Do not describe a row as available unless you have confirmed it some other way. Stored rows are not a guarantee of current selectability.
• Do not present a stored number as a prediction, a recommendation or an edge.
• Do not republish rows without permission. Technical access is not a redistribution license.