Throughout Timber's integration installation instructions you'll notice we require a set of credentials identified by
YOUR_SOURCE_ID . This document will explain each of these credentials parts and why we need both.
API keys provide access to Timber's API for your account. All API keys are scoped to the organization they belong to. You use them in the
Authorization header as the
Bearer strategy within your requests to the Timber API (see the the HTTP and API Keys section).
Timber's "sources" are a containers for log data and create a workspace for those logs. For example, each source has its own schema, alerts, and views. For more information, head over to the source management section.
Because an organization can have many sources, and an API key works across your entire organization, Timber requires an explicit source ID to properly route the data. Otherwise Timber has no way to know which source you want to write your log data to. In additional, this makes API key management simple since you do not need to store and manage source specific API keys.
Simply create a source within your organization. Your API key and source ID will be displayed on the installation page. Additionally, you can obtain an API solely, but it cannot be used for log ingestion without specifying a source ID.