Cisco.Api 3.0.176

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package Cisco.Api --version 3.0.176
                    


                    

                
NuGet\Install-Package Cisco.Api -Version 3.0.176
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Cisco.Api" Version="3.0.176" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Cisco.Api" Version="3.0.176" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Cisco.Api" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add Cisco.Api --version 3.0.176
                    


                    

                
#r "nuget: Cisco.Api, 3.0.176"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package Cisco.Api@3.0.176
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Cisco.Api&version=3.0.176
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Cisco.Api&version=3.0.176
                    


                            Install as a Cake Tool

Cisco.Api

Nuget License: MIT Codacy Badge

A .NET library for accessing Cisco Support APIs, including EoX, Product Information, PSIRT, PSS, Serial Number to Information, PX Cloud, and Umbrella APIs.

Prerequisites

You must have an SNTC (Smart Net Total Care) or PSS (Product Support Services) account in order to use this library.

Installation

Using .NET CLI

dotnet add package Cisco.Api

Using Package Manager Console

Install-Package Cisco.Api

Using Visual Studio

  1. Open your project in Visual Studio
  2. Right-click on the project and click "Manage NuGet packages"
  3. Search for "Cisco.Api"
  4. Click "Install" to add the latest version to your project

Using PackageReference

Add the following to your .csproj file:

<PackageReference Include="Cisco.Api" Version="*" />

Setup

Before using the library, you need to obtain API credentials:

  1. Go to the Cisco API Console
  2. Sign in with your SNTC or PSS account
  3. Click "Register a New App"
  4. Add a new Application, selecting the API endpoints that you intend to use
  5. Note the Client ID and Client Secret - you'll need these for authentication

Example Code

using Cisco.Api;
using System;
using System.Linq;
using System.Threading.Tasks;

namespace My.Project
{
	public static class Program
	{
		public static async Task Main()
		{
			var ciscoClient = new CiscoClient(
				new CiscoClientOptions
				{
					ClientId = "<YOUR_CLIENT_ID>",
					ClientSecret = "<YOUR_CLIENT_SECRET>"
				});

			var productInformation = await ciscoClient
				.ProductInfo
				.GetBySerialNumbersAsync(new[] { "<SERIAL_NUMBER>" })
				.ConfigureAwait(false);

			var productDetails = productInformation.Products.First();

			Console.WriteLine($"Product Name: {productDetails.ProductName}");
		}
	}
}

Supported Frameworks

  • .NET 9.0
  • .NET 10.0

API Documentation

The Cisco Support APIs documentation can be found here:

License

This project is licensed under the MIT License.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
3.0.176 107 9/3/2026
3.0.174 94 8/31/2026
3.0.151 142 8/28/2026
3.0.149 126 8/28/2026
3.0.127-ge8f1822b2d 129 6/22/2026
3.0.122 352 6/19/2026
3.0.119 143 5/29/2026
3.0.118 136 5/22/2026
3.0.117 599 4/16/2026
3.0.116 605 3/31/2026
3.0.115 600 3/31/2026
3.0.114 602 3/30/2026
3.0.111 606 3/29/2026
3.0.110 615 3/23/2026
3.0.104 684 2/20/2026
3.0.103 1,178 11/20/2025
3.0.94 970 11/17/2025
3.0.93 920 11/17/2025
3.0.92 917 11/17/2025
3.0.89 864 9/30/2025
Loading failed

Security fix: sensitive HTTP headers are now redacted in diagnostic output.

     Previously the request logging in CustomHttpClientHandler and CustomFastUmbrellaHttpClientHandler
     passed the whole HttpRequestMessage to the logger, and its ToString() renders every header. The
     Authorization header this client sets on each request was therefore written verbatim.

     This was not confined to Trace. LogErrorHeadersIfNeeded fires when Trace is DISABLED and
     OnErrorEnsureRequestResponseHeadersLogged is set, logging the whole request at Error level - so on
     a normal production logger a usable token reached the log store on every failed request.

     Authorization, Proxy-Authorization, Cookie, Set-Cookie and common API key headers are now redacted
     in request and response, along with any vendor-prefixed variant whose name ends in "Authorization".
     The scheme and credential length are retained, so failures remain diagnosable.

     Breaking change to message text: the Request and Response log messages are now rendered by the
     library rather than by HttpRequestMessage.ToString(). The shape is the same but code parsing those
     messages should be checked.

     Consumers should upgrade and then review existing logs for previously captured tokens.