Environments
Development and Production environments, and their endpoints.
Each application that uses Legation has its own environments. Users, sessions and settings in one environment are separate from the other.
| Environment | Purpose |
|---|---|
| Development | Build and test your integration. |
| Production | Serve real users. Production is activated separately, after a readiness checklist. |
Endpoints
Each environment has its own endpoint, which you pass to the client as baseURL. The endpoint includes the environment, an environment ID and the region.
https://dev-<environment-id>.<region>.<your-id0n-domain>
https://prod-<environment-id>.<region>.<your-id0n-domain>These show the form of an endpoint. Use the exact endpoint you receive for your environment. If the endpoint has no path, the client adds the default base path /api/auth. See Endpoints.
Keep environments separate
- Use the Development endpoint in local and test builds, and the Production endpoint in production builds.
- Store the endpoint as configuration, not in code.
- Register redirect URLs for each environment. See Origins and redirect URLs.
Availability
Creating applications and environments is available at release.