Markets and visibility

The Markets page shows operator-visible market data and lets scoped staff hide or show markets.

Dashboard path

Operator Dashboard → Operations → Markets

Required scope: markets:read

Mutation scope: markets:write

What operators can do

• search by market title or slug
• filter by visible or hidden
• inspect market status, YES percentage, trading cutoff, and operator-scoped 24h volume
• export all filtered rows as CSV
• copy the current page as HTML/plain text
• hide or show a market when the session has markets:write

Market visibility mode controls which markets operator users can access through Mini App surface.

Modes

How to choose

• use all for broad rollout with no market restrictions
• use allowlist for phased launch or regulated scope
• use blocklist when most markets allowed but few must stay hidden

Operational guidance

• treat visibility changes as production-impacting config
• validate expected market set after each change
• coordinate visibility changes with onboarding, compliance, or commercial rules

Verification

After change:

1. call GET /api/operator/markets
2. confirm expected list returned
3. launch test user and verify same market set in Mini App

API behavior

Visibility changes call:

POST /api/operator/markets/{id}/visibility

Body:

{ "visible": true }

Mode-specific behavior:

• allowlist: show inserts or updates an allow rule; hide deletes the rule.
• blocklist: hide inserts or updates a block rule; show deletes the rule.
• all: first hide switches operator mode to blocklist and inserts a block rule.

Common mistakes

• forgetting hidden markets still exist in broader platform
• changing visibility without re-running operator smoke checks
• assuming market visibility can fix wallet or webhook issues