Generate an API Key
To connect Logfire with StackOne you need an API key generated from your organization’s API keys settings in the Logfire console. An Organization key scoped to all projects is recommended so that project, dashboard, alert, variable, channel, and organization actions all work.
Sign in to Logfire
Sign in to the Logfire console for your data region.
- EU Region: Logfire EU console
- US Region: Logfire US console
Open Org settings and API keys
Click your organization name in the top-left corner of the page header to open the organization menu, then select Org settings. In the left settings sidebar under your organization, click API keys.

Create a new API key
On the API keys page, click + New API key in the top-right corner to open the New API key form.

Choose the key type and permissions
Enter a Name (and an optional Description), then configure the key.
- Key type: choose Organization so the key works across every project in the organization (recommended). Choosing Project instead ties the key to a single project selected in the Project dropdown and limits it to that project.
- Permissions: pick what the key can do. Click Select all, or enable the grouped categories the connector needs — Read (view dashboards, alerts, datasets, variables, and API keys), Manage (create and modify dashboards, alerts, datasets, variables, tokens, and API keys), and Org administration (manage invitations, API keys, trust policies, SCIM, audit logs, and billing).

Select individual scopes (optional)
For a more restricted key, expand Advanced and tick individual scopes under Organization Scopes and Project Scopes instead of whole categories. To cover every connector action, enable at least these scopes.
- View projects and their settings and Rename or delete projects and change their settings (project read/write).
- Ability to create projects within the organization (organization create project).
- Read notification channels across the organization and Create or modify notification channels across the organization (channel read/write).
- Read dashboards within a project and Create or modify dashboards within a project.
- Read alerts and SLOs within a project and Create or modify alerts and SLOs within a project.
- Read managed variables and prompts within a project and Create or modify managed variables and prompts within a project.

Set expiration and create the key
Set Expiration to No expiration (or choose a duration that suits your security policy), then click Create API key.

Copy the API key
The API key is shown only once after creation. Copy it immediately and store it securely, then paste it into the API Key field in StackOne Hub.
- The key starts with
pylf_v2_eu_(EU) orpylf_v2_us_(US). - If you lose the key you must create a new one.
Create a Project-Scoped API Key
A key scoped to a single project is created from that project’s own settings. You need one in either of two cases: as an alternative to the organization key (it works only within its own project — organization and channel actions are unavailable), or, more commonly, as an addition to it, because the variable-type actions require a project-scoped key. That second case is why StackOne Hub shows a separate optional Project API Key field.
Open Project settings and API keys
Open the project, then click Project settings in the breadcrumb and select API keys from the project settings sidebar. Click + New API key to open the form.

Configure the project key
The Project field is fixed to the current project (to create keys for other projects or the whole organization, use the organization API keys page link). Under Permissions, enable the scopes the key needs — Send telemetry, Read, and Manage — or expand Advanced for individual scopes. Set Expiration, click Create API key, and copy the key.

Enter it as the Project API Key in StackOne Hub
If this key is for the variable-type actions, paste it into the optional Project API Key field in StackOne Hub and leave the main API Key field set to your organization key — the two are used side by side. Under Permissions, the key needs the Variables scopes: project:read_variables to list and read variable types, plus project:write_variables to create them. Leave the field blank if you do not use those actions.
Minimum Scope to Connect
The minimum scope required to connect depends on the key type you choose. Grant additional scopes for the operations you plan to use.
- Organization API key (recommended) — minimum to connect:
organization:read. - Project API key — minimum to connect:
project:read. This key is limited to the single project it was created in. - Project API Key field (optional) — only for the variable-type actions:
project:read_variables, plusproject:write_variablesto create types.
Determine Your API Region URL
Logfire runs in two independent data regions. StackOne Hub asks for the API Region URL — the API base URL that matches the region where your Logfire account was created.
Identify your region and enter the API Region URL
Check the address bar while signed in to the Logfire console to identify your region, then paste the matching base URL into the API Region URL field in StackOne Hub.
- If the console URL is
logfire-eu.pydantic.dev, you are on the EU region. Enterhttps://api-eu.pydantic.dev - If the console URL is
logfire-us.pydantic.dev, you are on the US region. Enterhttps://api-us.pydantic.dev - Format:
https://{region-host} - Example:
https://api-eu.pydantic.dev
Linking the Account from the Hub
Navigate to the Hub
Fill out the fields
- API Key
- API Region URL
- Project API Key (optional — variable types only) (Optional)
Connect
- Click Connect
- If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
- Once authorization is successful, you will see a confirmation popup
If the account linking is successful, you will see the newly linked account in your Accounts page.