API keys
A key is created in ReachBoost under Integrations > API keys. It belongs to one workspace and has full access to it, with no per-user audit trail, so treat it as you would a password. The CLI stores it once and uses it for every later command.whoami shows which key and workspace commands will use and checks that they work.
Where the key is stored
The key never sits in a flag or in shell history. Where it goes depends on the platform.- macOS
- Linux
- Windows
The key is stored in the macOS Keychain under your user account.
Profiles
A profile holds one key and one default workspace.--profile <name>, or REACHBOOST_PROFILE, picks it; the profile called default is used when neither is given. An agency with several client workspaces, or a staging key next to production, keeps them apart this way.
Workspaces
A workspace key works for its own workspace. An agency key can act on the workspaces linked to it: list them, remember one as the default, or name one per command with--workspace.
Scripts and CI
In CI, setREACHBOOST_API_KEY from your secret store. A key that comes from the environment must be paired with an explicit workspace, from --workspace or REACHBOOST_WORKSPACE; a stored profile default is never mixed with it. The CLI says on stderr when it is using a key from the environment.
--stdin.

