Base URLs and environments
Keep production, staging, and embed URLs clearly separated when you integrate OmniLab.
This article explains how to keep production, staging, and embed URLs separated when you integrate OmniLab. The exact hostnames are tenant-specific, so use the values provisioned for your environment rather than copying a host from another deployment.
What OmniLab usually provides per environment
| Environment | Typical use | What you should receive |
|---|---|---|
| Staging | Build, test, and validate the integration | API base URL, experience domain, non-production credentials, and staging webhook targets |
| Production | Live participant traffic | Production API base URL, production experience domain, production credentials, and production webhook targets |
Keep three URL concepts separate
| URL type | What it is for | Example placeholder |
|---|---|---|
| API base URL | Token requests and approved server-to-server API calls | https://<api-host> |
| Experience domain | Landing pages, touchpoints, and embeds | https://experience.example.com |
| Host page or wrapper URL | Your own site, kiosk shell, or app container | https://www.example.com/promo |
The same integration often uses all three. Keeping them separate makes debugging much easier when a token request works but an embed URL does not, or when staging webhooks are accidentally pointed at production infrastructure.
Safe environment rules
- Never reuse production secrets in staging.
- Register separate webhook receivers per environment.
- Test booking flows, cancellations, and webhook retries in staging first.
- Keep test campaigns, public links, and downstream automations separate from production.
Staging API base URL: https://staging-api.example-brand.com
Staging experience domain: https://staging-experience.example-brand.com
Production API base URL: https://api.example-brand.com
Production experience domain: https://experience.example-brand.comDo not guess hostnames
Use only the hostnames issued for your tenant. Some deployments use branded domains, delegated domains, or environment-specific infrastructure that will not match another customer's setup.
Related
Authentication
Use the right token endpoint and credentials for each environment.
Iframe embedding
Use the correct experience domain when you embed OmniLab inside a web page.
Custom domain delegation
Plan branded experience domains before go-live.
Rate limits
Design your client to behave safely in each environment.