API Keys

API keys authenticate your requests to the Clipform API - for custom integrations, the MCP server, and platforms like Zapier and Make.

Create an API key

1. Open API keys in your dashboard settings.
2. Click Create API key, enter a Name (for example, "n8n workflow"), and confirm.
3. Copy the key straight away - for security it's shown only once.

To revoke a key, open API keys and choose Revoke on that key.

Key format

A cf_ prefix followed by 64 hex characters (256 bits of entropy) - so a key looks like cf_a1b2c3d4e5f6.... Keys are hashed (SHA-256) before storage, so Clipform never keeps the raw key, which is why it's shown only once.

Authenticate a request

Send the key as a Bearer token on every request:

curl -H "Authorization: Bearer cf_your_key_here" \
  https://api.clipform.io/v1/me

GET /v1/me (Get current user) is the quickest way to confirm a key works. For everything else, browse the API Reference.

Use with the MCP server

The MCP server authenticates with your API key instead of OAuth - handy for CI, scripts, and headless environments. Set it as an environment variable:

{
  "mcpServers": {
    "clipform": {
      "command": "npx",
      "args": ["-y", "@clipform/mcp-server"],
      "env": { "CLIPFORM_API_KEY": "cf_your_key_here" }
    }
  }
}

Full setup (IDEs, flags, OAuth) is on the MCP server page.

Keep keys safe

• Treat keys like passwords - never commit them to source control.
• Use a separate key per integration, so you can revoke one without affecting the others.
• Revoke a key the moment it's exposed, then create a new one.