Skip to content

Trade Pad

The Tradepad module (/tradepad) is the interactive pricing workspace: search for an instrument, load pricing context from the API, and drive instrument-specific pricing panels plus a scenario grid. It does not replace Trades (/trades) for blotter-style booking; use the Trades module when you need the booked grid, blotter feed, or New trade form.

TradePadInstrumentSelector resolves text (name, ticker, ISIN, etc.) against the instrument service. When a row is chosen, Atlas loads /atlas/instrument/pricing-context (see Dashboard for related context usage). A loading state shows while context is fetched; errors surface next to the selector.

If the server returns 404 (no back_office.instrument row for the id), the UI offers synthetic starters — Vanilla option, Bond, or Future / perp — so you can still build a manual pricing context and continue.

Depending on family / kind from the pricing context, Tradepad swaps the main panel:

ContextPanel
Bond-like (FI, BOND, …)Bond — YTM, risk metrics charts, PV sensitivity
Future-like (FUTURE, PERP, …)Future — contract pricing surface
Vanilla-style options (OPTION, … with supported families)Option — PV, Greeks charts, vol surface helpers

Panels share the same pricing-context payload; family detection is implemented in TradePadModule (see source under frontends/atlas-web/src/modules/tradepad/).

Below (or alongside, depending on layout) the main panel, TradePadScenarioGrid runs multi-dimensional scenarios (bumps/shocks) against the active context—use it to stress PV and greeks before committing to a ticket elsewhere.

Book, amend, and cancel flows are handled in Trades (booked grid context menu, New trade tab) or the Dashboard blotter, not inside Tradepad. Power tier rules described in Accessing Atlas apply to cancel/amend operations.

Quick JSON pricing experiments against POST /atlas/pricing/ticket and POST /atlas/pricing/scenario-grid are documented under Electronic trading (/etrade).