API Keys

API keys authenticate external applications that call your Blueprints. You need an API key for any integration that connects to Leapter at runtime, including the REST API, MCP connections, and n8n HTTP workflows.

Where to find API Keys

Click API Keys in the left sidebar of Leapter. This opens the API Keys management page.

The API Keys page showing a table of keys with name, permissions, status, and usage information — The API Keys page lists every key with its permissions, status, and usage.

The table shows all your API keys with:

Column	Description
Name	The friendly name you gave the key
Permissions	The projects the key can access
Key	The key prefix (the full key is only shown once at creation)
Status	Whether the key is Active or Revoked
Last Used	When the key was last used to make an API call
Created	When the key was created

Create an API key

Click Create API Key in the top right.
Enter a Key Name: a friendly name to help you identify this key later (e.g., “n8n Integration” or “Production API”).
Select one or more Projects the key should have access to. A single key can grant access to several projects. This is useful when one integration calls Blueprints from multiple projects.
Click Create Key.

The Create API Key dialog with fields for key name and project selection — Name the key and select the projects it can access.

After creation, the full API key is displayed. Copy it immediately. You will not be able to see the full key again. All keys start with the lpt_ prefix.

Edit which projects a key can access

You can change a key’s project scope without revoking it. This is useful when you add a new project that an existing integration should also be able to call.

Find the key in the table.
Click the three-dot menu on the right.
Select Edit projects.
Adjust the project selection and confirm.

The key keeps the same value. Anything authenticating with it continues to work, with access to the new set of projects.

Store your API key securely. If you lose it, you will need to create a new one. Never share API keys in public repositories or client-side code.

Use your API key

Pass the API key as a header in all requests to Leapter:

Header name: X-API-Key
Header value: your API key

For example, in a curl request that runs a Blueprint:

curl -X POST "https://lab.leapter.com/runtime/api/v1/{appspace}/{project-id}/models/{blueprint-id}/runs" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: lpt_your-api-key-here" \
  -d '{"input1": "value1"}'

Each integration page explains where to configure the API key for that specific tool:

MCP connections: set as a header in your MCP client configuration
REST API: pass as the X-API-Key header in HTTP requests
n8n HTTP Workflow: configure in the HTTP Request node’s authentication settings
n8n MCP Agent Workflow: set up as a Header Auth credential in the MCP Client node

Revoke a key

If a key is compromised or no longer needed, you can revoke it:

Find the key in the table.
Click the three-dot menu on the right.
Select Revoke.

Revoked keys stop working immediately. You can toggle Show revoked keys to see previously revoked keys.

What to do next

AI Protocol (MCP): connect AI assistants to your Blueprints
Web API (OpenAPI): call your Blueprints through a REST API
Deploy & Integrate: explore all deployment options

Get Started

Create & Edit Blueprints

Test & Validate

Track Changes

Release & Integrate

Monitor & Analyze

Workspace & Collaboration

Where to find API Keys

Create an API key

Edit which projects a key can access

Use your API key

Revoke a key

What to do next

​Where to find API Keys

​Create an API key

​Edit which projects a key can access

​Use your API key

​Revoke a key

​What to do next

Where to find API Keys

Create an API key

Edit which projects a key can access

Use your API key

Revoke a key

What to do next