API Key Usage

Monitor and analyze your API key usage to track integration activity, identify trends, and troubleshoot issues.

Accessing API Key Usage

Navigate to Settings > API Keys from your workspace. You'll see a list of all your API keys with their descriptions and last used timestamps. Each API key row includes action buttons for viewing usage statistics (chart icon), copying the key, and deleting the key.

To view detailed usage statistics for a specific API key, click the chart icon in the Actions column. This opens the API Key Usage dashboard for that particular key.

Usage Dashboard Overview

The API Key Usage dashboard provides comprehensive analytics for your API key activity. At the top of the page, you'll see the API key name and a "Back to API Keys" link to return to the main API Keys list.

Summary Metrics

The dashboard displays four key metrics in card format:

chevron-rightTotal Requestshashtag

Shows the total number of API calls made using this key. This includes all requests regardless of their outcome.

chevron-rightCompletedhashtag

Displays the count of successfully processed requests (shown in green). These are requests that received a valid response from the API.

chevron-rightFailedhashtag

Indicates the number of requests that encountered errors (shown in red). This helps identify potential issues with your integration.

chevron-rightRate Limited hashtag

Shows requests that were rejected due to exceeding the rate limit (shown in orange). If this number is high, consider optimizing your request frequency or contacting support for rate limit adjustments.

Analytics Charts

The dashboard includes three visualization sections to help you understand your API usage patterns:

chevron-rightBy HTTP Methodhashtag

Presents a donut chart breaking down requests by HTTP method (GET, POST, etc.). This helps you understand the types of operations your integration performs most frequently.

chevron-rightBy Response Statushashtag

Shows a donut chart categorizing requests by HTTP response codes. Common status codes include 200 (success), 429 (rate limited), and 503 (service unavailable). This visualization helps quickly identify if your integration is experiencing issues.

chevron-rightTop Endpointshashtag

Lists the most frequently called API endpoints with their request counts. This helps identify which parts of the API your integration uses most heavily and can guide optimization efforts.

Request Log

Below the analytics section, you'll find a detailed request log table that shows individual API requests. The table includes the following columns:

chevron-rightRequest ID hashtag

A unique identifier for each API request, useful for troubleshooting specific issues.

chevron-rightTimestamphashtag

Shows when the request was made, displayed in your local timezone.

chevron-rightMethodhashtag

Indicates the HTTP method used (GET, POST, etc.).

chevron-rightEndpoint hashtag

Shows the API endpoint that was called.

chevron-rightStatus hashtag

Displays the request status (completed, failed, etc.) with color-coded badges.

chevron-rightResponse hashtag

Shows the HTTP response code returned by the API.

Filtering Requests

The request log supports multiple filtering options to help you find specific requests:

chevron-rightFilter by resource IDhashtag

Allows you to search for requests related to a specific resource.

chevron-rightAPI key ID hashtag

Filter is pre-applied to show only requests for the current API key.

chevron-rightDatehashtag

Lets you narrow down requests to a specific time period.

chevron-rightStatushashtag

Shows only requests with a particular status (completed, failed, etc.).

chevron-rightHTTP method hashtag

Filter displays only requests using a specific HTTP method.

chevron-rightAPI endpoint hashtag

Shows requests to a particular endpoint.

chevron-rightResponse statushashtag

Displays requests with specific HTTP response codes.

Click Apply to apply your selected filters, or Clear filters to reset all filters. You can also use Edit columns to customize which columns are displayed in the table.

Managing API Keys

From the main API Keys page, you can perform the following actions:

chevron-rightGenerate API Keyhashtag

Creates a new API key for your workspace. Click the blue "Generate API Key" button in the top right corner. Give your key a descriptive name to help identify its purpose (e.g., "PowerAutomate", "Zapier Integration").

chevron-rightCopy API Keyhashtag

Copies the key value to your clipboard for use in your integrations.

chevron-rightDelete API Key hashtag

Permanently removes the API key. This action cannot be undone, and any integrations using this key will stop working immediately.

Best Practices

When managing your API keys, consider the following recommendations:

  • Use descriptive names for your API keys that indicate their purpose or the integration they're used for. This makes it easier to manage multiple keys and identify which key is used where.

  • Regularly review your API key usage to identify unused keys that can be deleted, reducing security risk.

  • Monitor the Failed and Rate Limited metrics to catch integration issues early. A sudden spike in failed requests may indicate a problem with your integration or changes to the API.

  • If you're consistently hitting rate limits, review your integration logic to reduce unnecessary API calls or implement request batching where possible.

circle-exclamation

Last updated