An API key lets a tool connect without asking you to sign in for every request. Treat it as a secret, and create it for a specific purpose you can recognize later.
This walkthrough is for organization admins. Do not give someone a key as a workaround for missing account permissions.
Create a key
- Open Organization Settings and choose API Keys.
- Select New Key and enter a recognizable name.
- Select Create.
- Copy the key when it is shown and store it securely. The full value is shown at creation, not as a normal reusable display field.
Personal Settings also has an API Keys area for eligible admins. When creating a key there, check the selected organization before choosing Create Key.
Connect and check the tool
Follow the connected tool's instructions for its authentication fields. For an MCP client, use the current Start Testing MCP instructions in the Manual; client capabilities and required headers can differ.
Start with a read-only request and check the organization and records returned. Before a bulk change, review the full target list and the intended fields. Afterward, open the affected records in Start Testing to check the result.
Do not assume every tool supports every web action or supplies its own approval prompts.
Replace or remove a key
Create and test a replacement before deleting an old key still used by a tool. Then use the old key's delete control in the key list. Deleting it can break any connection still using that credential.
If authentication fails, check the configuration without pasting the secret into a screenshot, chat, or support ticket. If the key may be exposed, replace it.