Tracking license utilization across multiple teams can be a manual hurdle for large organizations. In a recent technical working session, we explored how to efficiently export Applitools usage metrics via API to external platforms like ServiceNow. Centralizing this data allows Procurement and Asset Management teams to monitor contracts and actual consumption in real-time.
Understanding the Core Metrics
Applitools provides several granular metrics to help you understand your testing footprint. The primary billing and measurement factors discussed include:
- Monthly Checkpoints: Measured month-by-month rather than annually.
- Page Concurrency: The maximum number of pages being tested simultaneously.
- Component Concurrency: Specifically related to Storybook integrations.
- Tested Pages/Scenarios: A cumulative look at active scenarios within a 31-day window.
While metrics like total users and viewers are often unlimited, tracking the consumption of checkpoints per team ensures every department stays within the allocated contract limits.
The Integration Strategy: Moving Data to ServiceNow
The goal is to move beyond the Applitools UI and pull live data into ServiceNow tables for consolidated reporting.
1. Setup & Authentication
To begin, you must create a Service User within the Applitools Admin Panel.
- API Key: Generate a read-only API key for this user. This ensures the integration can fetch data without having write or execute permissions.
- Rotation: Security best practices suggest rotating this key every 90 days.
2. Data Retrieval via REST API
While Python is often used for initial testing, ServiceNow typically leverages JavaScript. The retrieval process follows a simple logic:
- Base URL: Use the Applitools public REST endpoint.
- Payload: Define the start_date, end_date, and the specific Account IDs you wish to query.
- Request Type: A standard POST request fetching a JSON response.
3. Mapping JSON Responses
The API returns a JSON array where each item contains an Account ID and a beginning date (time). This allows for distinguishing between multiple teams if you are fetching data in bulk. For example, the JSON field totalActiveScenarioChecks31Days directly maps to the “Tested Pages” count seen in the Applitools Dashboard.
Practical Benefits
By automating this flow, teams can adjust their resolution—viewing data per day, week, or month—directly within their primary management tool. This transparency helps identify usage spikes and ensures that “Unused” licenses are redistributed to teams that need them most. Ready to start your integration? Check the Applitools documentation for specific curl command structures to begin testing your API responses today.
Quick Answers
Integrating Applitools usage data with ServiceNow allows Procurement and Asset Management teams in large organizations to centralize data, monitor contracts, track license utilization across multiple teams, and view actual consumption in real-time.
You must create a Service User within the Applitools Admin Panel and generate a read-only API key. This key is used for fetching data and should be rotated every 90 days following security best practices.
Data retrieval is performed using a standard POST request to the Applitools public REST API endpoint, typically leveraging JavaScript within ServiceNow, though Python can be used for initial testing.
Automation creates transparency, enabling teams to adjust the data’s resolution (viewing data per day, week, or month) directly within ServiceNow. This helps identify usage spikes and ensures unused licenses can be efficiently redistributed.
