Keeping API keys and webhooks safe
Secret keys stay on servers, webhooks get verified, and rolling a key is normal maintenance.
Create keys under Developers. A secret key starts with bk_test_ or bk_live_ and is shown once, when it is created — keep it on your server, in a secret store, never in a repository, a mobile app or front-end code.
A key works only while the person who created it is an active member of the workspace, and only within their current role. Removing someone revokes every key they created; suspending them stops their keys until they are reinstated. So before someone leaves, have another owner or admin create replacement keys and switch your server over first. Also replace a key whenever a laptop goes missing or a key might have been logged: create a new one, switch your server over, then revoke the old one.
Verify every webhook signature before trusting the payload, and process events idempotently — deliveries are at-least-once and order is not guaranteed.
Give developers the developer role. It can manage keys and webhooks but cannot move money, which limits the blast radius of any single compromise.