Overview
Addigy retired its V1 API on March 31, 2026. To keep the Addigy Inspector working, we've migrated it to use Addigy's V2 API. This article walks through what changed, what you'll see in your environment after the update, and whether any action is required on your end.
Short answer for most partners: no action required. Your existing API key will continue to work, and inspections will keep running automatically. There is one expected, one-time side effect on the first inspection after the update, which is covered below.
Why this change happened
Addigy announced the retirement of its V1 API and removed it on March 31, 2026. Any integration still using V1 endpoints would have stopped collecting data after that date. We migrated all remaining V1 calls in the inspector (preflight validation, policy data, device data, and applications) over to their V2 equivalents.
What you'll see on the first inspection after the update
One-time wave of change detection alerts
This is the big one to be aware of.
In V1, Addigy returned device fields using Pascal Case with spaces (for example, Device Name, Serial Number, Total Memory (GB)). In V2, those same fields come back in snake_case (for example, device_name, serial_number, total_memory_gb).
Because Liongard sees those field names as new, change detection will fire alerts for every device field on the first inspection after the update. This is expected, it's one-time, and it does not reflect actual changes happening on your devices. After that first inspection, alerts will return to normal behavior.
If you have notification rules or webhooks tied to Addigy device changes, you may want to temporarily silence them, or just be ready for a louder than usual alert volume on the first run.
Removed and updated columns
A few columns were updated as part of the migration:
"Patches Applied" column has been removed. V2 does not expose an equivalent field, so we could not preserve this column.
"Days Since Last Cloud Backup" has been split into two separate columns: "Time Machine Days Since Last Backup" and "Days Since Last CrashPlan Backup". V2 reports these as separate facts, so splitting them gives you cleaner per-tool visibility.
Credential field cleanup
The inspector configuration used to ask for three credentials: CLIENT_ID, CLIENT_SECRET, and CLIENT_API_KEY. V2 only uses an API key, so:
CLIENT_IDandCLIENT_SECREThave been removed from the inspector setup.CLIENT_API_KEYis now the only credential needed.
This was already a required field, so existing configurations will keep working without any updates from you.
Bug fixes included in this release
While doing the migration, we also fixed a couple of pre-existing issues:
Parent policy name fix: The
parent_name_rfield on Policy Details was incorrectly showing the policy's own name instead of its parent. It now resolves to the correct parent policy name.Creation time fix for older policies: Some older Addigy policies don't have a
creation_timevalue populated, and Addigy returns these as0. The inspector was previously converting that to1970-01-01, which was misleading. These now correctly show as no value (null) instead.
Do I need to do anything?
For most partners, no. Your inspector will continue running on its normal schedule with the credentials you already have configured.
You may want to:
Let your team know to expect a one-time spike in change detection alerts on the first inspection after the update, so they don't chase it as a real incident.
Review any notification rules, webhooks, or automations tied to Addigy device change events and consider muting them for that first run if the noise would be disruptive.
If you were relying on the "Patches Applied" column, note that it is no longer available.
Frequently asked questions
Why are all my Addigy devices showing change detection alerts at once? This is the expected one-time behavior described above. Addigy renamed their device fields in the V2 API, so Liongard sees them as new fields on the first inspection. The alerts will not repeat after the first run.
Do I need to reauthenticate or get a new API key? No. Your existing CLIENT_API_KEY continues to work with V2.
What happened to my CLIENT_ID and CLIENT_SECRET? V2 doesn't use them, so they were removed from the inspector configuration. Nothing was lost; those credentials just aren't needed anymore.
Where did the "Patches Applied" column go? It was removed because V2 does not provide an equivalent data source. We were not able to preserve it.
Will my historical Addigy data still be there? Yes. Historical inspection data is preserved. The change detection alerts on the first run after the update reflect the field name change, not data loss.
Who do I contact if something looks off after the migration? Reach out to Liongard Support through your normal channel and reference the Addigy V2 migration.