Skip to main content
An API key belongs to one account. Reactor bills a session to the account whose key started the session. Switch the dashboard to the team before you create a key. The team then pays for all that the key does.

​
API keys per team

Reactor binds each API key to one account at creation. The binding never changes. A key from your personal account cannot start sessions on the balance of a team. A team key cannot spend from your personal account.
1

Switch to the team

Open the account menu and select the team under Switch account. A key can carry only the roles you hold in that team. The SDKs and the CLI need the developer role.
2

Create the key

Open the API Keys page and create a new key. The dialog names the account that owns the key. To create a key for another account, switch to that account first.
3

Copy and store the key

The key starts with rk_, like each other key. Store the key with the other secrets of your team. Do not commit the key to source control.
The API Keys page lists every key you own, from your personal account and from each team. Each row names the account that owns the key. Only Create key follows the account you selected. A team key stops working in two cases:
  • The person who created the key leaves the team, or an admin removes that person.
  • Reactor deactivates the team.
The keys from your personal account and from your other teams continue to work.
Name each key after the thing that uses it, for example Production or CI. When a member leaves and their keys stop, the team can then see what will break.

​
The CLI

reactor auth login creates a key in the same way. The approval page in your browser asks which account the login is for. The page lists each account you belong to. You can select only an account where you hold the developer role. The CLI binds the new key to the account you select. See Log in to a team.

​
Billing per team

Each team has its own balance, payment method, and invoices. These are separate from the personal account of each member. Switch to the team to see them on the Billing page.
  • A session that a team key started draws from the balance of the team. Reactor never bills the member who created the key.
  • Account admins and billing admins buy credits for the team and manage its payment method. Developers can see the balance but cannot add to it.
  • The Usage page shows the sessions of the account you selected. The usage of a team is one view. Your personal usage is another view.
The prices, the meter, and the rules to add funds are the same for each account. See Pricing & Billing. Session quotas also apply per account. See Rate limits.