> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jobin.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# How to create and manage API keys in Jobin

> Create an API key or MCP token for a tool, copy it safely, review every key in the workgroup, and delete one the moment you no longer need it.

To create an API key, click **New API Key** on the **Integrations** page, choose the integration, name the key, click **Generate API Key**, and copy it right away. Jobin shows it only once.

API keys and MCP tokens let your tools act on your Jobin workspace. You create and manage all of them on the
[Integrations page](https://my.jobin.cloud/workgroups/integrations).

Each key belongs to the workgroup where you create it. The **Active Keys** counter in the page header shows how many
the current workgroup has.

## What this gets you

* Each tool gets its own key, so you can revoke one without affecting the others.
* You see every key and token for the workgroup in one table.
* Deleting a key stops it working immediately.

## Create an API key

**1. Start a new key**

Click **New API Key** in the page header. To create a key for a specific app, click **Connect** on its card instead.

**2. Select the integration**

Under **Select Integration**, choose the app the key is for, or **Custom integration** for your own tool.
This step is skipped when you start from an app's card.

**3. Label the key**

Enter an **API Key Label**. Choose a descriptive name that tells you what the key is for.

**4. Generate it**

Click **Generate API Key**.

**5. Copy the key**

Copy the key from the confirmation window, then click **I've Saved My API Key Securely**.

> [!WARNING]
>
> Jobin shows the full key only once. Store it securely. If you lose it, delete the key and create a new one.

## Create an MCP token

If your assistant can open a browser sign-in, you don't need a token. Add the MCP URL in the assistant instead.
Create a token only for headless clients and server-side agents.

1. Click **Connect** on the **Jobin MCP** card.
2. Enter a token label. If you leave it blank, Jobin names it **Jobin MCP token**.
3. Choose permissions. **Read** access is always on. Tick **Write access** to allow supported write tools.
4. Click **Create token** and copy it.

The confirmation window also shows the URL and header to configure in your client. For the full setup, see
[Connect with an MCP token](/connect-mcp-token.md).

> [!NOTE]
>
> API keys can't be used for MCP. Create a separate MCP token for MCP clients.

## Review your keys

Open the **API Keys** tab to see every key in the workgroup.

| Column | What it shows |
| - | - |
| **Label** | The name you gave the key. |
| **Integration** | The app the key is for. MCP tokens also show **Read** or **Write** badges. |
| **Key** | A masked value. API keys start with `sk_`, and MCP tokens start with `mcp_`. |
| **Created** | The date you created it. |
| **Actions** | A delete button. |

If the workgroup has no keys yet, the tab says **No API keys yet** and offers **Browse integrations**.

## Delete a key

1. Open the **API Keys** tab.
2. Click the delete icon on the key's row.
3. Confirm **Delete this API key?**

The key stops working immediately, and the deletion can't be undone. Any tool still using the key will start receiving
`401` errors, so update those tools first or create a replacement key.

## Security best practices

* Store keys securely and never expose them in client-side code.
* Rotate keys regularly: create a new key, update your tool, then delete the old one.
* Give each tool its own key so you can delete one without affecting the others.
* Only give write access to MCP clients you trust.

## Ideas to get more from it

* Rotate keys regularly: create a new key, update the tool, then delete the old one.
* Give MCP clients read access only, unless they need to change data.

## Use your key

> **[API authentication](/api-reference/authentication.md)**
>
> Send your key in the `x-api-key` header.

> **[Custom integration](/integrations-custom.md)**
>
> Each integration's page explains how to use its key.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.