Endpoints we provide
There are two environments you can integrate with: Sandbox and Production. Our sandbox environment is a fully functional environment that allows you to test your integration before going live. The sandbox environment is a completely separate environment from the production environment. This means that any data you create in the sandbox environment will not be available in the production environment.
To test your integration we will provide you with a client ID and client secret for the sandbox environment as well as multiple user accounts. These accounts will have different roles and permissions so you can test your integration with different types of users. Once you are ready to go live, we will provide you with a client ID and client secret for the production environment.
All Sandbox API endpoints are hosted at *.sandbox.eduplaces.dev
and all Production API endpoints are hosted at *.eduplaces.io .
For example, the authentication endpoints are available at https://auth.sandbox.eduplaces.dev/ in the Sandbox environment and https://auth.eduplaces.io/ in the Production environment.
To switch between the Sandbox and Production environments, you do not need to change your code. Just change the base URL of the API endpoints you are calling and use the client ID and client secret for the environment you are calling.
URLs by environment
| Service | Sandbox | Production |
|---|---|---|
| Authentication via OpenID Connect | https://auth.sandbox.eduplaces.dev/ | https://auth.eduplaces.io/ |
| API endpoints for everything else | https://api.sandbox.eduplaces.dev/ | https://api.eduplaces.io/ |
| User Interface | https://portal.sandbox.eduplaces.dev/ | https://portal.eduplaces.de/ |
OpenID Connect Discovery
| Environment | URL |
|---|---|
| Sandbox | https://auth.sandbox.eduplaces.dev/.well-known/openid-configuration |
| Production | https://auth.eduplaces.io/.well-known/openid-configuration |
The OpenID Connect Discovery document contains metadata about our OpenID Connect implementation. To validate ID tokens, the document contains an URL to our JSON Web Key Set (JWKS) endpoint. The JWKS endpoint contains the public keys used to sign ID tokens. Common OpenID Connect libraries can use the OpenID Connect Discovery document to configure themselves automatically.