Manage your account's API and SDK keys on the **API & SDK Keys** page of the **Developer Workbench** in the RiskOS™ Dashboard. Your API keys and SDK keys appear together on this page.

- [Access Sandbox keys](https://riskos.sandbox.socure.com/developers/key-management).
- [Access Production keys](https://riskos.socure.com/developers/key-management).

> 📘
>
> **Note**:
>
> RiskOS™ supports multiple API keys for rotation. Each key has access to all workflows. To create a new key, contact Socure Support.

## API keys

RiskOS™ authenticates API requests with Bearer tokens. The **API Keys** table lists each key with its **Key Name** and status ( **Active**, **Deprecated**, or **Expired**), a masked **Token**, the **Created On** date, and the **Created By** user.

**Actions**

- **Show or hide a token**: Click the eye icon to reveal or mask the token.
- **Copy a token**: Click the **Copy token** icon.
- **Download a token**: Click the **Download** icon to save the token as a text file.
- **Regenerate a key (security rotation)**: Click the **Regenerate** icon on an **Active** key. This icon is disabled while a **Deprecated** key exists. Delete the deprecated key first.
- **Delete a key**: Click the **Delete** icon on a **Deprecated** key.

> 📘
>
> **Important note on regeneration**:
>
> When you regenerate a key, RiskOS™ instantly creates a new **Active** key and marks the current key as **Deprecated**. Both the new **Active** key and the **Deprecated** key function until you explicitly delete the deprecated key. This allows for a zero-downtime rotation.

## MCP keys

RiskOS™ uses an MCP Server Key to authenticate to the RiskOS™ MCP Server, which connects AI development tools such as Cursor and Claude Code to your account. The **MCP Keys** table uses the same **Key Name**, status, **Token**, **Created On**, and **Created By** columns as the API keys table.

If you have no MCP keys yet, click **Generate MCP Key** to create one. Each MCP key supports the same show, copy, download, regenerate, and delete actions as an API key.

For client setup and configuration, see [Integrate using Cursor / Claude Code (MCP Server)](https://help.socure.com/riskos/docs/riskos-mcp-server).

## SDK keys

RiskOS™ uses a single SDK key to initialize both the Digital Intelligence and Predictive Document Verification SDKs. The **SDK Keys** table shows each key's **Label**, a masked **Key**, its **Status**, and the **Last Used** date.

**Actions**

- **Show or hide a key**: Click the eye icon to reveal or mask the key.
- **Copy a key**: Click the **Copy key** icon.
- **Edit a label**: Click the **Edit label** icon to open the **Edit SDK Key Label** dialog, then enter an optional label to identify the key.

## Next steps

Now that you have your credentials, continue your integration:

- [Integrating with RiskOS™](https://help.socure.com/riskos/docs/integrating-with-riskos) — send your first evaluation request, handle the response, and validate your integration end to end.
- [Sandbox and Production environments](https://help.socure.com/riskos/docs/environment) — confirm which environment your keys target before you send live requests.
- [Integration guides](https://help.socure.com/riskos/docs/integration-guides) — production-ready guides for onboarding, fraud prevention, and other use cases.
- [Webhooks](https://help.socure.com/riskos/docs/webhooks) — receive real-time results for asynchronous evaluations.

Updated 17 days ago