Changelog

API keys let you select individual actions, such as viewing customers, creating charges, revoking them, and requesting refunds. Granting one action does not select the others automatically. You can edit permissions without replacing the secret, and each item has a description and a Learn more link.

In Authorized applications, consent and permission editing use the same individual choices. Editing lets you remove and restore access from the original authorization; other operations require new consent. Account rules and the current permissions of the person who authorized access still apply.

Creating a key requires identity confirmation before opening the form when there is no valid authorization. That authorization is reused when creating the key while it remains accepted. If confirmation is needed again when saving, creation continues with the completed form without another click. Employees can copy a Sandbox secret or rotate a key only when their access covers all actions granted to it.

Raims CLI 0.1.4 and the documentation console also align environment selection with the authentication method. With an API key, the key determines the company and environment. With OAuth, the operation must accept the requested environment and the connection must authorize it. In the CLI, --environment is exclusive to OAuth; simulations remain restricted to Sandbox.

To update the CLI through npm, run npm install -g @raimshq/cli@latest. See API keys, Authorized applications, and Authentication to review your integration's access.