Environments

Wolfx runs all your requests in the context of an environment. By default, Wolfx creates two environments when your account was just created, development and production.

Development environment

The development environment is used for testing purposes and validating notification changes prior to committing them to the production environment.

Production environment

It will be your live/production environment, you cannot make changes to this environment directly. You will first have to make the changes in the development environment and then promote it to production. This is a read-only environment.

Data associated with environments

Wolfx will separate most of the data associated with your account based on the current accessed environment.

• Subscribers
• Workflows
• Execution logs
• Connected providers

Each environment will be accessed using a separate credential set:

• Application Identifier - This is a public identifier used in client-side applications to identify your application. It is unique to an environment in an organization and is different from Provider Identifier.

• API Secret Key - A secret key used when communicating with the Wolfx API from your backend services.

We suggest configuring these key sets based on your active environment, the same as you would use to manage different service credentials and serve them based on the current environment in which your code is deployed.