Teams
Everything you buy or use belongs to a team, not to a person: the credit balance, the API keys, the usage history, the monitors and the billing. Every account starts with a team of one, and you can invite others to it.
- Every key on a team draws from the same credit balance.
- Requests are rate limited per team; see Rate limits.
- Usage by key and by endpoint is in the dashboard and through Request history.
Roles#
There are three roles. The person who creates the team is its owner.
| Can | Owner | Admin | Member |
|---|---|---|---|
| See the team, members, usage and keys (names only) | yes | yes | yes |
| Create API keys | yes | yes | |
| Revoke and rotate API keys | yes | yes | |
| Buy packs and start a plan | yes | yes | |
| Open the billing portal, change or cancel the plan | yes | ||
| Refund an unused pack | yes | ||
| Invite members | yes | yes | |
| Invite admins | yes | ||
| Remove members (admins can remove members only) | yes | yes | |
| Change roles | yes | ||
| Transfer ownership | yes | ||
| Delete the team | yes |
Admins can do the everyday work (keys, credits, inviting and removing members). Only the owner manages billing, refunds and roles, and can transfer ownership or delete the team. Owners can remove anyone except themselves; transfer ownership first.
Invites#
Owners and admins invite people by email from the dashboard. An invitee signs in with the invited address (email, Google or GitHub) and joins as the role they were invited with. Only the owner can invite admins.
Keys#
A team can hold up to 20 active keys, each with a name and a last-used time. See Authentication for rotating and revoking.
Free credits#
The 100 free credits are granted once per person, when they first sign up. Creating or joining more teams does not grant more, and disposable email domains do not qualify.
Closing a team#
Deleting a team revokes its keys, cancels its subscription and forfeits its remaining credits. Export what you need from your usage history first.