Overview 💥
Addigy has completed the retirement of its API v1 platform. Since the Addigy Legacy Inspector depends on API v1, it is no longer able to successfully retrieve data from Addigy.
The good news is that Liongard already provides a replacement—the Addigy Inspector, which uses Addigy's API v2 and is fully supported.
This article explains:
Why this change is happening
Whether you're affected
What the impact is
How to migrate to the supported inspector
What to expect during the transition
Why is this changing?
Addigy has deprecated and removed support for API v1 in favor of API v2.
This is a change made by Addigy not Liongard. Because the Legacy Inspector communicates exclusively through API v1, it can no longer collect information once that API is unavailable.
The current Addigy Inspector has already been updated to use API v2 and is the recommended inspector for all Addigy integrations moving forward.
Am I affected?
You are affected only if you're using the Addigy Legacy Inspector.
To verify which inspector you're using:
Open the Liongard portal.
Navigate to Admin → Inspectors.
Locate your Addigy system.
Check the Inspector Type.
Inspector | Status | Action Required |
Addigy | ✅ Supported | No action required |
Addigy (Legacy) | ⚠️ Deprecated | Migrate to the Addigy Inspector |
If you're already using the Addigy Inspector, there's nothing you need to change.
What happens if I continue using the Legacy Inspector?
Because the Legacy Inspector relies on API v1, inspections will no longer be able to retrieve data from Addigy. This may result in:
Failed inspections
Missing or stale device information
Outdated documentation
Missing alerts
Incomplete reports
Visual Insights dashboards no longer receiving updated Addigy data
Existing historical inspection data isn't immediately removed, but no new data will be collected until you migrate.
✅ Benefits of migrating
Migrating to the current Addigy Inspector allows you to continue using Liongard without interruption. Benefits include:
Continued inventory collection
Continued documentation updates
Support for Addigy's current API
Ongoing compatibility with future Addigy enhancements
Improved long-term reliability
Continued alerting and reporting with better data visibility
Continued Monitoring
⭐️ Before you begin
Before configuring the new inspector, make sure you have:
Administrator access to your Addigy account
Permission to create API tokens
Access to your Liongard environment
Creating an Addigy API Token
The current Addigy Inspector uses API v2. To create an API token:
Sign in to Addigy.
Navigate to Account → Integrations.
Select New API Token.
Create the token.
Copy the generated token for use in Liongard.
Note ‼️
You no longer need separate API v1 Client IDs or Client Keys. The current inspector authenticates using the API token generated through the Integrations page.
Configuring the Addigy Inspector
Once you've generated your API token:
In Liongard, navigate to Admin → Inspectors → Inspector Types.
Select Addigy.
Choose Add System.
Complete the inspector configuration.
Enter your Addigy API Token.
Save the configuration.
Run an inspection to verify connectivity.
After the first successful inspection, confirm that devices and policies are being collected as expected.
Recommended migration process
For the smoothest transition, we recommend following this order:
Step 1 : Create the new Addigy Inspector.
Step 2 : Run an inspection.
Step 3 : Verify that expected devices, policies, and other information are being collected.
Step 4 : Review any reports, automations, or Visual Insights dashboards that reference Addigy data.
Step 5 : Once you've confirmed the new inspector is working correctly, retire or remove the Addigy Legacy Inspector.
Following this process helps ensure there is no interruption to your monitoring.
What happens to my historical data?
Historical inspection results collected by the Legacy Inspector remain available according to Liongard's standard data retention policies. If you rely on historical reports or dashboards, we recommend confirming that the new inspector is collecting data successfully before retiring the Legacy Inspector.
Additional Resources
Liongard Documentation
Addigy Documentation
If you have questions during the migration or need assistance configuring the new Addigy Inspector, our Support team is happy to help.