I’m trying to connect a third-party tool to the API, but I don’t have a key to authenticate requests.

This feature documentation explains how API authentication keys are used when connecting third-party tools to the API. It clarifies what you need to authenticate requests and why authentication is required for secure access.

When connecting a third-party tool to the API, an authentication key is typically required to verify your identity and authorize requests. This helps protect your data and prevents unauthorized access or misuse of the API. To use a third-party integration, you first need to obtain the appropriate API key (or other supported credential) from the product’s API access area. Once you have a key, you configure the third-party tool by pasting the key into its API connection settings and selecting any required options such as environment or region. Requests sent by the tool must include the key in the required location (for example, as an HTTP header or query parameter), depending on the API’s authentication scheme. If you don’t have a key, you may need to request one from an administrator, ensure your account has API access enabled, or follow the product’s key issuance process. This documentation is intended to help you understand what is needed before you begin integration work and to reduce setup delays caused by missing credentials. It is particularly useful for teams adopting new automation, analytics, monitoring, or ETL tools that rely on authenticated API calls. By ensuring authentication is configured correctly, you can establish stable, secure connections and avoid repeated request failures.