Environments
Introduction
This section describes the various Sage Active environments available to you.
For each environment, you will find the role, API domain, and main URLs for authentication using the SBCAuth service.
During testing, you must use the Sage Active stage environment, and for production, you can choose between the French, Spanish, or German products based on your preference for developing an application for a specific market or multiple markets.
Please note the difference in legislation organization:
Stage
- In the stage environment, only one environment from which you can test in all three legislations:
FR
,ES
, andDE
. - Each user is associated with a tenant, and the tenant determines the legislation.
- From stage, you can test your application for any of the legislations:
FR
,ES
, orDE
. - When defining your application to obtain API keys and authentication, you can specify which market or markets your application should function in, using in stage the same API for all three legislations.
-
You will need a Sage ID account of type sandbox.
This account must be associated with a user who has authorization in Sage Active stage.Sage Active Stage Environment (Testing Only)
- The Sage Active Stage environment is exclusively reserved for testing purposes.
- Accessing Sage Active Stage requires a Sage ID sandbox account, which is different from a production Sage ID account.
-
In Postman environnement baseAddress = API Address without
/graphql
.API AddressAuthUrlAccessTokenUrlRevoke Token URL stage
Production
- However, in production, there are three distinct environments:
FR
,ES
, andDE
. - When defining your application to obtain API keys and authentication, you can specify which market or markets your application should function in, using a different API for each legislation.
- For example, you can choose to operate solely in
FR
, or in [FR
,ES
], or only inES
, or across all markets [FR
,ES
,DE
]. -
For each production environment
FR
,ES
, andDE
, you will require a Sage ID account of type production.
This account should be associated with a user who has authorization in the respective Sage Active production environment.- Do not use the production environment for your tests.
- Accessing Sage Active Prod requires a Sage ID Production account, which is different from a sandbox Sage ID account.
-
In Postman environnement baseAddress = API Address without
/graphql
.API AddressAuthUrlAccessTokenUrlRevoke Token URL prod
- Do not use the production environment for your tests.
- Accessing Sage Active Prod requires a Sage ID Production account, which is different from a sandbox Sage ID account.
-
In Postman environnement baseAddress = API Address without
/graphql
.API AddressAuthUrlAccessTokenUrlRevoke Token URL prod
- Do not use the production environment for your tests.
- Accessing Sage Active Prod requires a Sage ID Production account, which is different from a sandbox Sage ID account.
-
In Postman environnement baseAddress = API Address without
/graphql
.API AddressAuthUrlAccessTokenUrlRevoke Token URL prod