Cisco.Api 3.0.217

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


                    

                
NuGet\Install-Package Cisco.Api -Version 3.0.217
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.217" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Cisco.Api" Version="3.0.217" />
                    


                            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.217
                    


                    

                
#r "nuget: Cisco.Api, 3.0.217"
#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.217
#: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.217
                    


                            Install as a Cake Addin
                        

                    

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


                            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 net11.0 is compatible. 
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.217 40 2026/11/11
3.0.216 46 2026/11/10
3.0.212 167 2026/10/27
3.0.211 185 2026/10/22
3.0.184 474 2026/9/20
3.0.183 148 2026/9/20
3.0.179 178 2026/9/12
3.0.176 179 2026/9/3
3.0.174 143 2026/8/31
3.0.151 172 2026/8/28
3.0.149 164 2026/8/28
3.0.127-ge8f1822b2d 143 2026/6/22
3.0.122 419 2026/6/19
3.0.119 164 2026/5/29
3.0.118 154 2026/5/22
3.0.117 618 2026/4/16
3.0.116 621 2026/3/31
3.0.115 617 2026/3/31
3.0.114 621 2026/3/30
3.0.111 622 2026/3/29
Loading failed

Fix: EoX lookups by serial number now build a valid request on Refit 15.

     IEox.GetBySerialNumberAsync marked its serialNumber parameter [Body] while the URL template
     still declared a {serialNumber} path segment. Refit 13 allowed a single parameter to satisfy
     both, so the request was correct and the conflict was invisible. Refit 15 does not, and every
     call now fails inside the client, before anything is sent, with "URL
     /supporttools/eox/rest/5/EOXBySerialNumber/{pageIndex}/{serialNumber} has parameter
     {serialNumber}, but no method parameter matches".

     If you are on Refit 15, take this version: EoX by serial number does not work at all without
     it. If you are still on Refit 13, the outgoing URL is unchanged, including the escaping of
     comma-separated serial numbers, so upgrading is safe and costs you nothing except a stray
     text/plain body that was being attached to a GET.

     Every other Refit method in the library was checked for the same URL template and parameter
     attribute conflict. There were none, so no other call site changes.

     This package now depends on Refit.Reflection. Four of its interfaces, IEox among them, cannot
     be generated inline by Refit's source generator, and on Refit 15 the reflection request
     builder is no longer included by default. Without it, constructing a CiscoClient throws
     rather than merely failing on those calls. Declaring the dependency here means you inherit it
     instead of discovering it at runtime.

     New offline tests build a request for every Refit method in the library, so a URL template
     that no parameter can satisfy now fails this library's own build rather than surfacing as a
     runtime exception in your application.