Workspaces and keys
Updated
A workspace groups your API keys, usage, limits and Playground.
The key and its calls belong to one workspace. Review its usage.
Keys and usage
Create a named key under API keys and copy it when it appears. The key and its calls belong to that workspace. See Authentication for the header and Rate limits for refusals.
Open Usage on your workspace's Overview and choose a period to compare text cache hit rates in Requests by key. See Text caching.
Usage separates answered decisions, replays, failed calls and unavailable calls. Recent requests show metadata such as the request ID, status and error code; they do not show the request content or answer.
Roles
| Role | Actions |
|---|---|
| All roles | Read the workspace, run Playground, create keys, revoke their own keys and leave. |
| Owners and admins | Revoke any key, manage invitations, rename the workspace and remove ordinary members. |
| Owners | Remove privileged members, change roles, manage billing and schedule workspace deletion. |
A workspace must keep an owner.
Invitations
Owners and admins manage invitations. Sign in to the console to use the actions available to your role.
Cancel and restore
An owner can schedule workspace deletion in Settings after signing in again. Keys and open invitations are revoked. Restoring the workspace leaves those keys revoked.
Deleting a workspace does not delete your sign-in identity. Use the privacy policy for identity deletion and personal-record requests.