urlscan.io Blog

Today we are announcing detailed activity insights for teams and API keys. The activity insights show users the quota consumption of each API key, and whether any of these API keys are generating errors when calling our APIs.

Activity tracking tracks the following information per API key and per user:

• The number of requests for: Search API, Result API, Scan API, Livescan
• The last activity timestamp for each of these actions
• Activity statistics available in: minute, hour, day, and month granularity
• Response count grouped by status code: HTTP/200, HTTP/400, HTTP/404, HTTP/429
• The last HTTP User-Agent header observed - This helps to identify the system or code making those requests
• The last IP address observed using this key - This helps to identify the system or code making those requests

Activity tracking is shown in the urlscan.io UI on the API key management and team management pages.

Structured information is available via the following endpoints:

• /api/v1/activity/user
• /api/v1/activity/team

Background

Over the years we have worked with hundreds of customers, some of whom are using urlscan and urlscan Pro with with dozens or even hundreds of individual team members. Those types of customers would typically also have multiple API keys active at any one time: One for their SOAR platform, another one for integration testing, yet more keys for individual research projects. A frequent issue that came up was that customers would eventually lose track of where all of their API keys were active and how much each API key was consuming of their account-wide quota.

The new Activity tracking feature will help urlscan customers to identify issues with their automated urlscan usage more quickly and more confidently.