Dashboard configuration

Set theme, copy, enabled networks/assets, and flow once in the Pulse dashboard — no frontend deploy required.

Everything in Theming and the embedded iframe’s flow option can also be set once in the Pulse dashboard instead of in code. The config is stored against your partner record, resolved from your API key when a session is created, and delivered to the embed on the client-session response — so a dashboard change reaches every mount immediately, with no frontend deploy.

// partner_config — carried on the client-session response
{
  "enabled_networks": ["base", "polygon"], // subset of the full network set
  "enabled_assets": ["USDT"],
  "theme": { "primary_color": "#083a9a", "mode": "dark", "density": "compact" },
  "strings": { "title": "Fund your safe" },
  "attribution": "none", // never mandatory
  "flow": "select", // default when the mount doesn't pin one
}

Precedence and narrowing

• Defaults ← dashboard config ← mount options. Anything you pass to mount() (theme, strings, flow) wins over the dashboard value for that mount; the dashboard fills whatever the mount leaves unset.
• Network/asset lists only narrow. No config means the full set — every supported network and asset. enabled_networks/enabled_assets shrink that set; a mount may shrink it further (networks: ["base"], assets: ["USDT"]) but can never re-enable something the dashboard disabled.
• The server enforces the lists. Session creation and in-flow re-selection reject disabled values with network_not_enabled / asset_not_enabled — the embed’s picker merely mirrors what the API will accept.

Sandbox stand-in

In the local sandbox the dashboard doesn’t exist yet — stand it in with:

POST /sandbox/config
{ "partner_config": { ... } }

Send "partner_config": null to clear it.