API keys page

API keys let external automations, scripts, and services call the STYD API on behalf of a workspace.

Where API keys are managed

API keys are created and managed from the API key generatorin the Docs → API section. Keys belong to the workspace that is active when you generate them.

What they are for

Use an API key with automation platforms such as Make or n8n, with custom scripts, or with any backend service that calls the STYD API. The key is sent in the x-api-key request header.

Handling keys safely

A new key is shown in full only once, when you create it. Copy it then and store it securely. Treat keys like passwords: never share them, never commit them to source control, and never expose them in client-side code.

Give each key a clear label so you know where it is used.

Revoke keys you no longer use. Revoked keys stop working immediately.

If a key is ever exposed, revoke it and generate a new one.

A workspace can hold up to 5 active keys. If you reach the limit, revoke an old key before creating a new one. Only owners and admins can create or revoke keys. A key acts as a member of the workspace, and owners and admins can read the conversations it started.

Using the API

How to call endpoints, authenticate, and handle responses is covered in the API section. This page is only about where keys live and how to handle them.