Environments
The test and live environments, how their keys differ and what to do when an environment is closed.
Plutera has two environments: test and live. API responses call them TEST and LIVE. Use the test environment to write and debug your integration, and the live one for real work.
The key defines the environment
Requests have no "environment" parameter, and both environments share one API address. The environment is determined by the key that signs the request.
| Test environment | Live environment | |
|---|---|---|
| Key prefix | ak_test_ | ak_live_ |
environment field in responses | TEST | LIVE |
| API address | https://api.plutera.io | https://api.plutera.io |
A key of one environment never turns into a key of the other: to work in both, you need two keys. You cannot mix up environments through the address, only through the keys. Keep the test and live keys in separate stores and give the live key only to the live server.
You can tell a key's environment by its prefix and by the response of the key check.
What depends on the environment
Today the service list depends on the environment: a service appears in it only if it is ready to work in the key's environment. The test and live keys of one merchant may get different lists, and that is not an error.
An environment can be closed
An administrator opens environments for a merchant, each one separately.
A request with a key of a closed environment gets a 403 error with the rule environment_closed. The key itself is fine, you do not need to change it. If the merchant itself is not active, the rule is merchant_not_active. Both errors are described in the error catalogue.