Create and manage API keys to authenticate your integrations with Leapter.
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.
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 — useful when one integration calls Blueprints from multiple projects.
Click Create Key.
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.
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.