Staging server
Table of Contents
What is the staging server
Alongside our production API, we run a staging server. It is a pre-production environment you can use to test your integration against a near-production version of our API, without needing to work against production data or affect production users.
Available services
Staging exposes the same services as production, on the staging.infoflora.ch subdomain instead of infoflora.ch:
| Service | Production | Staging |
|---|---|---|
| Observations | obs.infoflora.ch |
obs.staging.infoflora.ch |
| Auth | auth.infoflora.ch |
auth.staging.infoflora.ch |
| Invitation | invitation.infoflora.ch |
invitation.staging.infoflora.ch |
| Validation | validation.infoflora.ch |
validation.staging.infoflora.ch |
| Fieldbook | fieldbook.infoflora.ch |
fieldbook.staging.infoflora.ch |
Authentication
Authentication on staging works exactly like on production: the same OAuth2.0 flows, the same client registration process, and the same scopes. There is no separate staging account or credentials scheme — simply point your requests to the staging hostnames listed above (e.g. https://auth.staging.infoflora.ch/oauth2/token instead of https://auth.infoflora.ch/oauth2/token).
Data
Staging is refreshed with a full copy of production data every morning. This means the data you see on staging is real production data, not synthetic or anonymized test data — handle it accordingly.
Daily reset
Staging is reset every day between 03:00 and 04:00. During this window the environment may be unavailable, and any data you created or modified on staging during the day is wiped and replaced by the fresh copy of production data.
Performance
Staging may run on lower-spec infrastructure than production. Response times and throughput on staging should not be used as a reference for production performance or capacity planning.