
Gleap uses a handful of keys and IDs, and they're easy to mix up. This page lists each one, where it lives in the dashboard and what it's for. Every value belongs to one project, so open the right project first. The API keys and identity keys are on pages only project admins can open. API keys and the server API need the Team plan or higher.
What | Where | Used for |
|---|---|---|
Project ID | Settings → Project → General, and the install pages under Settings → Widget → Install | Initialising the Gleap SDK in your website or app, and the |
API keys | Settings → Developer → API keys | Every server route: the v3 API, the |
Identity keys | Settings → Security → Customer identity → Identity keys | Signing identity tokens on your server |
MCP server URL | Settings → Developer → MCP | Connecting Claude, Cursor, ChatGPT and other AI tools |
Every SDK is initialised with the Project ID, for example Gleap.initialize("YOUR_PROJECT_ID") on the web. API calls send it in the Project header. It identifies the project, not a user, so it's fine for it to sit in your website or app code.
Go to Settings → Project → General.
Copy the Project ID.
The install pages show it too. Go to Settings → Widget → Install, choose Install myself and pick your platform to get a setup snippet with the Project ID already filled in.
API keys belong to service accounts. Requests made with a key act as that service account, and its name shows next to everything it does. One API key works for every server route: the v3 API (Authorization: Bearer header), the /admin/… and /recordings/… routes and the Segment destination (Api-Token header or HTTP basic auth), and the Conversations API (server-to-server).
Go to Settings → Developer → API keys.
Click Generate API key.
Give the service account a Name, and optionally an Avatar.
Click Create service account.
The new key appears in the list with a copy button. If your workspace can use more than one data region, the same page shows a Data region row with the API host to call.

Send the API key and your Project ID with every v3 request:
curl https://api.gleap.io/v3/tickets \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Project: YOUR_PROJECT_ID"Projects in the US region call https://api.us.gleap.ai instead. A key only works in its own project's region.
Keys that start with grk_ still work and show in the list as Older key. New keys of that kind can't be created. The same page has the switch Accept the project secret on the server API, which is on by default for existing projects.

Your server signs a short identity token for each logged-in user with an identity key, and your app passes it to the SDK with setUserJwt, so nobody can pose as one of your users. See Identify users and send attributes and events.
Go to Settings → Security → Customer identity → Identity keys and click Create key.
Give the key a label and pick the platform it may sign for.
Copy the key ID and the secret. Gleap shows the secret once.
A project holds up to five identity keys. To rotate one, create a new key, switch your backend to it, then retire the old one. Code for each server language is in the developer guide Customer identity.
Every project member can open Settings → Developer → MCP. The Server URL is the same for all projects in a region. AI tools that support sign-in connect with just the URL: you pick the project when you sign in, and the tool acts with your role. For a client without sign-in support, the page shows two headers to send instead, an API key and the Project ID. The key then acts as its service account. See Connect an AI assistant with the Gleap MCP server.