Skip to main content
In the Customer Dash, open Developer → API keys, select a key, then open its activity details. The view records requests across the whole public API—not only product inventory calls. Service actions, DNS writes, provisioning requests, panel-access operations, and other operation routes appear when they use that key. For account-wide totals and charts, use Home → Usage and spending. That page summarizes recorded API usage together with other account activity; per-key request details remain under Developer → API keys.

​
What the activity view shows

  • Request time and HTTP method.
  • Route, including operation endpoints.
  • Response status.
  • Source IPv4 address.
  • Request identifier when available.
  • Charts grouped by time, route, status, and source IPv4.
Use the filters and charts to spot unexpected routes, repeated failures, traffic outside the intended schedule, or an unfamiliar IPv4 address. Activity metadata is an audit aid; it is not a copy of request bodies or secrets.

​
Respond to suspicious activity

  1. Revoke the key immediately.
  2. Preserve request IDs, timestamps, routes, statuses, and source IPv4 values.
  3. Check the affected resource in the Customer Dash or its dedicated management application.
  4. Create a replacement with fewer scopes, a shorter expiration, and the required IPv4 allowlist.
  5. Contact support with sanitized evidence if an owned resource changed unexpectedly.
An IPv4 allowlist restricts where the key can be used. It does not replace expiration, least-privilege scopes, secret storage, request confirmation, or activity review.

​
ConvertSuite API activity

ConvertSuite gateway requests are included in the same per-key activity feed. Look for the convertsuite.* operation name and /v1/convertsuite/* route. The successful prepare request is the billable ConvertSuite operation; tool discovery, job polling, starting, and cancelling are recorded for audit but do not reserve another ConvertSuite operation.