Getting Started
Environments and base URLs
How environment-specific base URLs are handled without changing URL paths.
Environments and base URLs
OpenPoly documentation uses one contract for both staging and production.
Rule
Only URL paths are documented here.
- Paths do not change between environments.
- Request bodies do not change between environments.
- Response bodies do not change between environments.
- Wallet adapter and webhook contracts do not change between environments.
The operator documentation itself has explicit, isolated Worker targets:
| Environment | Documentation URL |
|---|---|
| Staging | https://operator-docs-staging.openpoly.app |
| Production | https://operator-docs.openpoly.app |
The staging Worker uses its dedicated staging D1 binding and does not fall back to the production Worker, route, site URL, or content database.
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.
What does not change
POST /api/operator/launchGET /api/operator/usersGET /api/operator/marketsGET /api/operator/tradesGET /api/operator/resolutionsGET /api/operator/balance-operations- 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.