Environments and base URLs
Environments and base URLs
OpenPoly documentation uses one contract for both staging and production.
Rule
API examples use paths relative to your provisioned Beacon/operator API base URL. Dashboard page paths belong to the dashboard origin; they are not API endpoints.
- Shared API paths and payload contracts stay stable across environments.
- Feature availability and product enablement depend on the deployed version and operator configuration.
- Simulator APIs and hosted failure scenarios are restricted to staging/local environments.
- Never copy production credentials, users, or wallet records into staging to reproduce an incident.
Documentation sites:
| Environment | Documentation URL |
|---|---|
| Staging | https://operator-docs-staging.openpoly.app |
| Production | https://operator-docs.openpoly.app |
What changes by environment
- Base URL for OpenPoly operator-facing endpoints.
- Base URL for Mini App launch host.
- Operator API key values.
- Wallet adapter secret values.
- Webhook secret values.
- Operator dashboard configuration values.
- Enabled products, permissions, rollout state, and isolated business records.
What does not change
POST /api/operator/launchGET /api/operator/usersGET /api/operator/marketsGET /api/operator/tradesGET /api/operator/resolutionsGET /api/operator/balance-operationsGET /api/operator/market-pnland read-only Cash Flow Triage under/api/operator/market-pnl/issues- Opinion reports under
/api/operator/settlement-report - Staff-only support resources under
/api/operator/support-tickets - Enabled Polyflight reporting resources under the
/api/operator/polyflight/prefix - Wallet adapter request paths
- Webhook headers and event envelope
Delivery model
OpenPoly provides environment-specific base URLs during onboarding and inside operator dashboard context.
Do not hardcode production hostnames into application logic. Treat base URL as environment config.
Keep Beacon/API, dashboard, Mini App client, and operator-owned wallet/receiver URLs as separate configuration values. Do not send a server API key to the documentation site or embed it in a launch URL. A feature described here is not evidence that it is enabled for your operator or approved for production.