> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/instruments-and-integrations/other-release-notes/novaseq6k-api-v3.2.1-release-notes.md).

# NovaSeq 6000 API-based v3.2.1

## Compatibility

* BaseSpace Clarity LIMS v4.2 or later. Not compatible with v6.0 and later.
* NGS Extensions Package v5.18 or later.
* Pre-configured Workflow Package (PCWP) v1.2 or later.

## Illumina NovaSeq Software Compatibility

* NovaSeq Control Software (NVCS) v1.6.0.

## Features to Note for this Release

This release of the BaseSpace Clarity LIMS integration package provides:

* API-based integration between NovaSeq instrument and BaseSpace Clarity LIMS.
* Support for asymmetric sequencing read length.
* Support for the newly launched SPrime (SP) flowcell.
* Support for long read sequencing (2x250) on SPrime (SP) flowcell.
* Updated workflow (NovaSeq 6000 v3.0) delivered directly from PCWP v1.2
* Direct file and information exchange between Clarity LIMS and NovaSeq Control Software (NVCS) via API includes the following:
  * From LIMS to NVCS:
    * Sample sheet generated on LIMS to NVCS
    * Run recipe generated on LIMS to NVCS
  * From NVCS to LIMS:
    * Run status updates (RunStarted, RunCompletedSuccessfully, RunEndedByUser, RunErroredOut) from NVCS to LIMS
    * Run metrics information from NVCS to LIMS

## Known issues

* In the run metrics payload that NVCS v1.6.0 sends to Clarity LIMS:
  * ReadsPF information is currently not available. (This will be fixed in the upcoming NVCS release.)
  * R2 error rate, R2 Q30, and R2 yield have slight inconsistency compared to values on Illumina Sequencing Analysis Viewer (SAV) software.


---

# 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://help.bioinsight.illumina.com/clarity-lims/instruments-and-integrations/other-release-notes/novaseq6k-api-v3.2.1-release-notes.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.