Environments can also be managed in the KeyStone Dashboard under Settings > Environments - no code required.
create / list / get / update / deactivate
Deactivation blocks credential access once it commits and closes the environment
to new settlements: resting instructions no longer match, and no repo closing
settlement is derived while it is inactive. Settlements already in flight keep
advancing to completion, and their webhooks keep delivering.
auth0_client_id must be an M2M application your Keystone operator has already
created and authorized against the Keystone API. Keystone verifies this before
saving the environment: a client id that is not authorized for the Keystone API
(including a client id that does not exist, or one belonging to a different API)
is rejected with 422 UNRECOGNIZED_CLIENT, and an empty value is rejected as a
validation error. The same check runs on secret rotation.Environment fields
Webhook delivery is configured per endpoint under
webhooks, not on the environment.