Skip to main content
The API Activity page shows the latest 200 API and MCP requests across your account, newest first. Use it to debug an integration or check what an agent called.

What the Page Shows

One table, with no filters, lists each request’s:
  • When
  • Project
  • Key
  • Method
  • Endpoint - for MCP calls, the tool name with an MCP badge
  • Status
  • Scope
  • Latency
  • Error - the error code, or the rate-limit state
Older requests drop off as new ones arrive, so a busy account may see only the last few minutes.

Common Workflows

Debugging an integration

  1. Open API Activity
  2. Scan the Endpoint and Project columns for the failing calls
  3. Check Status, Scope and Error: a 403 with the wrong scope means the key needs that scope
  4. Check the Key column to confirm the expected key made the call

Retiring a key

A key missing from the latest 200 requests may still be in use. Check Last used on API Keys before you revoke it.

Reviewing agent behavior

  1. Confirm agents or automations call only the expected endpoints and MCP tools
  2. Check response status and latency
  3. Check that each key’s scopes match the access it needs

Permissions

API Activity is available on plans that include API access.

Best Practices

  • Use distinct API keys for distinct integrations so the log stays attributable
  • Check API Activity after changing scopes or rotating secrets
  • Review rate-limited or error-heavy endpoints before widening access

Next Steps

  • API Keys - Create, scope, or revoke keys
  • Authentication - Review how keys and scopes work
  • Webhooks - Pair outbound event delivery with inbound API usage