---
title: "Nureva Console release notes - November 25, 2024 | Nureva support"
slug: "nureva-console-release-notes-nov-25-2024"
description: "This release focused on the Nureva Developer Toolkit and the switch from WebSocket-based local API to a REST (Representational State Transfer) architecture. "
tags: ["2024", "Nureva developer toolkit", "Release notes", "Nureva Console"]
updated: 2025-01-28T21:50:16Z
published: 2025-01-28T21:50:16Z
canonical: "support.nureva.com/nureva-console-release-notes-nov-25-2024"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.nureva.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Nureva Console release notes - November 25, 2024

With this release we did not introduce any new features, make any changes or add improvements to Nureva Console. This release focused on the Nureva Developer Toolkit and the switch from WebSocket-based local API to a REST (Representational State Transfer) architecture.

## Nureva Developer Toolkit

Nureva has switched from a WebSocket-based local API to a REST (Representational State Transfer) architecture. This update includes new endpoints for the HDL310 and HDL410, replacing sound location data and other commands with REST and Server-Side Events (SSE). The WebSocket API is now deprecated and will no longer receive updates. We recommend transitioning to the new local REST API, which is actively maintained.

REST is commonly used for control APIs, while SSE offers a similar solution to WebSocket for pushing API notifications to third parties, reducing unnecessary polling and simplifying development. SSE uses standard HTTP protocol, making it more familiar to developers and reducing communication overhead.

Documentation has also improved with a new language pane that provides code samples in multiple languages and the ability to interactively "try" each endpoint, features previously available only with our console APIs.

### Known Issues

There is a known issue with the "try it" widget: if the request is correct, it works fine. However, if there's a mistake, it will hang instead of showing an error. Since the "try it" feature forms the request for you, the user would have to manually make it incorrect to encounter this issue, making it unlikely. We are investigating the root cause.

### Additional Resources

#### Nureva Developer Toolkit

- [Start using the Nureva Developer Toolkit](https://developers.nureva.com/)

#### WebSocket local API guide

- [Previous API Guide PDF](https://support.nureva.com/docs/nureva-websocket-local-api-guide)