Identify audio components

Allows clients to identify audio components. For HDX devices, the port number of the audio component to be identified must be specified. For HDL310 and HDL410 devices the port number should not be specified.

admin role required

NOTE: Only supported for HDL310, HDL410, and HDX devices.

NOTE: For HDL310 and HDL410 devices, the request body should be empty.

Example Request Body for HDX

{
  "port": 1,
}
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Headers
string
required

Identifier for the integration application or service. This is intended for you to specify the name of your integration. Use this same value every time your integration calls into the Nureva device. There is no strict format as long as the value is limited to 500 characters. For example, "MyCompany Integration", "Power API", "SyncMaster", "Cloud Orchestrator", "Ultimate Audio Overlord" are all acceptable values.

string
required

Identifier for the integration version. This is intended for you to specify the version of your integration application or service. There is no strict format as long as the value is limited to 500 characters. For example, "1", "2.0", "1.5.2", "beta", "1.0.0-alpha", "1.0.0+20250102" are all acceptable values.

Body Params

The request body to identify audio components.

The request body for the component identification POST endpoint.

number

For HDX devices, the port of the audio component being identified. This property should not be provided for HDL310 and HDL410 devices.

Responses
200

Success

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json