> For the complete documentation index, see [llms.txt](https://nso-docs.cisco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nso-docs.cisco.com/resources/nso-resources/developer-support.md).

# Developer Support

Information on developer support.

The official [Cisco Crosswork NSO support page](https://www.cisco.com/c/en/us/support/cloud-systems-management/network-services-orchestrator/series.html) covers:

* Product Information
  * At-a-glance
  * Datasheets
  * End-of-life and end-of-sale notices
* Security Notices
  * Bulletins
  * Security advisories
  * Field notices
* Troubleshooting and Support Information
* Product Literature
  * Case studies
  * Solution overviews
  * White papers

## API Updates <a href="#api-updates" id="api-updates"></a>

To stay updated with the latest releases, refer to the [Cisco Network Services Orchestrator Changes](https://software.cisco.com/download/home/286331402/type/286283941/release/6.3) file available on [software.cisco.com](https://software.cisco.com/).

To compare the changes between the two NSO versions, refer to the [Cisco NSO Changelog Explorer](https://developer.cisco.com/docs/nso/changelog-explorer/?from=4.7\&kind=All%20non-backwards%20compatible).

## Community <a href="#community" id="community"></a>

If you have generic questions, chances are big that someone in the NSO Community can help you out.

Share your question on the [NSO Developer Hub](https://community.cisco.com/t5/nso-developer-hub/ct-p/5672j-dev-nso).

## Technical Assistance <a href="#technical-assistance" id="technical-assistance"></a>

The Cisco TAC team can support you with questions regarding NSO. The first file below will instruct you on how to open a service request. The second file includes more information about what needs to be included and explains more about why that information is needed. The third file is overall information from Cisco TAC on how to get support.

### Opening an NSO Service Request with Cisco TAC

{% embed url="<https://pubhub.devnetcloud.com/media/nso/docs/documentation/NSO-TAC.pdf>" %}

### Detailed Process for NSO and NED Support

{% embed url="<https://pubhub.devnetcloud.com/media/nso/docs/documentation/NSO-and-NED-support.pdf>" %}

### Cisco TAC Support Guidelines

{% embed url="<https://pubhub.devnetcloud.com/media/nso/docs/documentation/nso-tac-support-guide.pdf>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://nso-docs.cisco.com/resources/nso-resources/developer-support.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
