Skip to main content
Creating an Organization API key requires organization admin access in Logfire.

​
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.

1

Sign in to Logfire

Sign in to the Logfire console for your data region.

2

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.

Logfire organization menu opened from the top-left header, with both the organization selector and the Org settings menu item highlighted
3

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.

Logfire API keys page with the New API key button highlighted
4

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).
New API key form showing Key type set to Organization and the Read, Manage, and Org administration permission categories
5

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.
Advanced section expanded on the New API key form showing individual Organization and Project scope checkboxes
6

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.

New API key form showing the Expiration field and the Create API key button highlighted
7

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) or pylf_v2_us_ (US).
  • If you lose the key you must create a new one.

​
Minimum Scope to Connect

Set the key scope when you create it. Minimum to connect: Organization management (organization:read), which the connection test uses. Add the scopes for the operations you plan to use — note that listing projects additionally needs Project settings (project:read).

  • Organization management — organization settings, invitations and creating projects.
  • Notification channels — notification channels and alert schedules. Organization keys only.
  • Project settings, Alerts management, Dashboards management, Variables management, Write tokens management — available to organization and project keys alike.
  • Query telemetry (project:read_otlp) — not available on this connection type at all. Connect a Project API Key for log, trace and metric queries.
  • Instance administration (instance:admin) — self-hosted Logfire only; the instance-organization actions return HTTP 403 on Logfire Cloud.

​
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.

1

Enter the API Region URL for your region

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. Enter https://api-eu.pydantic.dev
  • If the console URL is logfire-us.pydantic.dev, you are on the US region. Enter https://api-us.pydantic.dev
  • Format: https://{region-host}
  • Example: https://api-eu.pydantic.dev

​
Linking the Account from the Hub

1

Navigate to the Hub

Use one of the three Linking Account Methods to access the Hub.
2

Fill out the fields

Fill out the following fields using details from your provider:
  • API Key
  • API Region URL
3

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.