Skip to main content

Cisco Umbrella | Deprecation of Legacy API

Cisco, Cisco Umbrella, Cisco API, Deprecation of Legacy API

Updated over 3 weeks ago

Overview 💥

Cisco officially retired their Legacy Umbrella APIs (Management, Reporting, Network Devices) on September 1, 2023. As part of this change, Liongard updated the Cisco Umbrella Inspector to support the new Umbrella API framework, requiring partners to update their API credentials prior to the cutoff.

This article explains the background, what changed, expected behavior, and how to resolve ongoing Inspector failures related to the API migration.


Why Does This Happen? 🤔

Beginning September 2023:

  • Legacy Umbrella APIs stopped responding.

  • Legacy API keys were removed from Liongard’s configuration.

  • New Umbrella API keys and secrets became mandatory.

  • Any inspector still using old credentials will fail with a setup or authentication-related error.

Cisco’s announcement:
(Reference: Cisco Umbrella – API Deprecation Notice)


What Liongard Changed 🌟

Liongard removed support for legacy API keys on August 31, 2023.
Inspector updated to require new Umbrella API Key + Secret.
Partners were notified to update their credentials prior to API retirement.
Inspectors configured with new credentials continue to work normally.

Inspectors that still contain legacy API credentials will fail until new credentials are added.


Current Resolution Status 👨‍💻

Status

Details

Migration Completed

Liongard fully transitioned to the new Cisco Umbrella API on schedule.

New API Required

Inspectors must use the new Umbrella key + secret. Legacy keys will no longer authenticate.

Functioning Inspectors

Any inspector updated with new credentials should operate normally.

Failing Inspectors

If the inspector was not updated, it will continue to fail with “setup issue” or API errors.

If you’ve already updated to the new key + secret, no action is required.


Troubleshooting Steps 🧑‍🏫

If your Cisco Umbrella Inspector is still failing, follow the steps below:

1️⃣ Confirm Your API Credentials

Verify that:

  • You are using the new Umbrella API key + secret

  • Credentials are assigned the required permissions

  • They correspond to the correct Umbrella organization

Cisco reference: (Adding Umbrella API Credentials — New API version)

To confirm the failure source:

  1. Run inspector in Clear Cache + Debug

  2. Review logs for:

Common errors you might see:

401 Unauthorized – Invalid API Key 
403 Forbidden – Insufficient Permissions
404 Not Found – Legacy endpoint unavailable Setup Issue: Umbrella API authentication failed

If the logs reference legacy API endpoints, your credentials were not updated.

3️⃣ Validate the API Endpoint & Configuration

Ensure the inspector is using:

Setting

Expected Value

API Type

Cisco Umbrella (New API)

API Key

New Umbrella API Key

API Secret

New Umbrella API Secret

If you still see legacy fields, please reach out to support team.

4️⃣ Try Replacing the Key & Secret

Sometimes Umbrella keys:

  • Expire

  • Are rotated by Cisco

  • Lose assigned scopes

Generate a fresh key + secret and update the Liongard inspector.

5️⃣ Check Cisco Umbrella API Availability

Cisco occasionally reports API outages or regional issues.
If your new credentials look correct but still fail, it may be due to Cisco service degradation.


Expected Inspector Behavior (After Update) 🚀

Behavior

Explanation

Inspector passes

New key + secret working correctly

Inspector fails immediately

Wrong key, wrong secret, or missing permissions

Inspector fails intermittently

Possible Cisco API issue or umbrella outage

Legacy field missing

Expected — legacy fields were removed by Liongard


When to Contact Support 🦁

If failures persist after following all steps above, contact Liongard Support.

Provide the following:

  • Environment Name.

  • Inspector Name.

  • Status error message.

  • Full Clear Cache + Debug log.

  • Screenshot of your current Umbrella API settings.

  • Confirmation of the new API key + secret.

  • Timestamp of last attempted run.

Our Support team is happy to help 😇
💬 Start a chat with Leo (Our AI Assistant) or connect with a live support engineer.
📧 Email: support@liongard.com


Additional Resources 🤩

‼️Note : We occasionally include third-party documentation to assist with troubleshooting. These resources are not maintained by Liongard, and we cannot guarantee their accuracy or availability. Please use them at your own discretion.

Did this answer your question?