Skip to navigation
Platform 101Monitor your integration

API Integrations Dashboard

View as Markdown

The Developer Console API Integrations Dashboard provides a real-time view of your integration’s performance and operational health. While the legacy API dashboard provides account-level summaries, the integrations dashboard enables telemetry analysis at the individual integration key level and helps troubleshoot issues with better precision.

The dashboard helps you monitor API traffic trends, track success and error rates, identify endpoint-level failures, and troubleshoot issues such as authentication failures or rate limiting.

This feature is currently in open beta. For more information on access and migration logic, see Migration and availability.

Overview

The dashboard is designed to provide immediate visibility into integration activity and operational health. It can help answer questions such as whether API traffic is increasing unexpectedly, whether error rates are rising, or which endpoints are generating failures.

API integration dashboard

Key metrics and modules

  • Traffic timeline: A visual representation of your API request volume over the last 24 hours, 7 days, and 30 days, helping identify traffic spikes and usage patterns.

  • Status code breakdown: A categorical view of response types:

    • Success (2xx): Confirms your integration is communicating correctly.
    • Client errors (4xx): Often indicate authentication issues (401), rate limiting (429), or malformed requests (400).
    • Server errors (5xx): Indicates an issue on the platform side.

  • Top endpoints: Identifies which API methods are most frequently called by the selected integration key, along with associated success and error rates.

Troubleshooting

The real-time nature of this dashboard enables rapid debugging. For example, a spike in 401 Unauthorized responses may indicate issues with access token generation or refresh logic, while an increase in 429 responses may indicate rate-limiting activity.

Migration and availability

The telemetry and management capabilities available in the Developer Console depend on how and where your integration key was originally created.

To ensure full visibility for all of your apps and access to the latest features, always create new integration keys directly within the Developer Console. Integration keys created using the legacy Apps and Keys experience may not be reflected within the Developer Console if your account has not yet promoted an app to production.

Migrated keys (Legacy)

If your integration key was promoted to production using the legacy Apps and Keys experience, it is automatically migrated to the Developer Console.

The integrations dashboard automatically displays available production telemetry for migrated keys, including API call volume, success and error rates, endpoint activity, and operational monitoring data. No additional migration steps are required for production integrations.

Integrations on the demo environment must be migrated manually. See Migrate integrations on demo to the Developer Console for details. After migration, integrations will support the full feature set described in the next section.

Native Developer Console keys

Integration keys created natively in the Developer Console support the full open-beta feature set, including:

  • Unified development and production telemetry
  • Environment switching between Demo and Production views
  • Full access to open beta management capabilities
  • Guest developer management features

Because these keys are built on the new Developer Console infrastructure, they provide a more complete end-to-end integration management experience.

Next steps