Integrators on Innosonix Docs

Maxx Control REST: Set channel names

Mon, 01 Jan 0001 00:00:00 +0000

Use the Maxx Control REST API to get and set channel names so zones and automation UIs stay readable. Names can contain alphanumeric characters, spaces, and special characters.

Get Channel Name

Retrieve the current name of a channel:

curl -X 'GET' http://${IP}/rest-api/settings/channel/1/name

{
 "value": "Living Room Left"
}

Set Channel Name

Set or update the name of a channel. Channel names can be up to 256 characters and support:

Maxx Control REST: Control device mute and volume

Mon, 01 Jan 0001 00:00:00 +0000

Use the Maxx Control REST API to set device-level master mute, master volume, and startup mute on one amplifier. These controls affect all channels globally — useful for emergency mute, master volume, and safe startup behavior.

Device Mute

The device mute acts as a master mute that affects all channels, regardless of individual channel mute settings.

Get Device Mute State

curl -X 'GET' http://${IP}/rest-api/settings/device/dsp/mute

{
 "value": false
}

Set Device Mute

curl -X 'PUT' http://${IP}/rest-api/settings/device/dsp/mute \
-H 'Content-Type: application/json' \
-H 'token: f4005bf8507999192162d989d5a60823' \
-d '{
 "value": true
}'

curl -X 'PUT' http://${IP}/rest-api/settings/device/dsp/mute \
-H 'Content-Type: application/json' \
-H 'token: f4005bf8507999192162d989d5a60823' \
-d '{
 "value": false
}'

Device Volume

The device volume acts as a master volume control that affects all channels. Individual channel volumes are relative to this setting.

Device Information

Mon, 01 Jan 0001 00:00:00 +0000

Getting Device Information

The device information endpoint provides details about your amplifier model, available channels, installed options, and hardware features.

Get Device Information

Retrieve all device information with a simple GET request:

curl -X 'GET' http://${IP}/rest-api/info/device

{
 "model_name": "MA32D",
 "channel": 32,
 "options": ["IF1", "IF2", "D1", "D2"],
 "psu_fan": true,
 "housing_fan": true
}

Understanding the Response

model_name: The amplifier model (e.g., MA32D, MA32LP, MA24D2)
channel: Number of available channels (16-32)
options: Array of installed options:
- IF1, IF2, IF3: Interface options
- D1, D2, D3: Dante options
- M1: Additional options
psu_fan: Whether PSU fan is installed
housing_fan: Whether housing fan is installed

This information is useful for:

Maxx Control REST: Enable or disable EQ

Mon, 01 Jan 0001 00:00:00 +0000

Use the Maxx Control REST API to enable or disable channel EQ (eqenable) — bypass the whole equalizer for testing or mode changes while keeping filter settings intact.

Enable EQ for Multiple Channels

Enable the equalizer for multiple channels in a single request:

curl -X 'PUT' http://${IP}/rest-api/settings/channel/ \
-H 'Content-Type: application/json' \
-H 'token: f4005bf8507999192162d989d5a60823' \
-d '[
 {
 "channel_id": 1,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 },
 {
 "channel_id": 2,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 },
 {
 "channel_id": 3,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 }
]'

[
 {
 "channel_id": 1,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 },
 {
 "channel_id": 2,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 },
 {
 "channel_id": 3,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 }
]

Disable EQ for Multiple Channels

Disable the equalizer for multiple channels:

Mute Control

Mon, 01 Jan 0001 00:00:00 +0000

Channel Mute Control

Mute control allows you to silence individual channels or the entire device.

Get Channel Mute State

Check if a channel is currently muted:

curl -X 'GET' http://${IP}/rest-api/settings/channel/1/dsp/mute

{
 "value": false
}

Mute a Single Channel

Mute a specific channel:

curl -X 'PUT' http://${IP}/rest-api/settings/channel/1/dsp/mute \
-H 'Content-Type: application/json' \
-H 'token: f4005bf8507999192162d989d5a60823' \
-d '{
 "value": true
}'

{
 "value": true
}

Unmute a Single Channel

Unmute a specific channel:

REST API

Mon, 01 Jan 0001 00:00:00 +0000

Every amplifier exposes a hierarchical JSON REST API used by Maxx Control itself and by third-party systems. Prefer this API for single-device integration. For project-level multi-amp control, use the Maxx Remote HTTP API instead.

Base URL and transport

Item	Value
Scheme / port	`http://` on port 80
Base path	`/rest-api`
Example	`http://${IP}/rest-api/settings/channel/1/dsp/mute`

Methods you will use most: GET (read), PUT (write / partial update), OPTIONS (allowed ranges and constraints), plus POST / DELETE on a few resources (for example EQ bands).

REST API

Mon, 01 Jan 0001 00:00:00 +0000

Goal / when to use

Drive day-to-day control (levels, mutes, selections) from a media controller or similar. Prefer this over scraping the GUI.

Where is the full reference?

Each Maxx Remote instance ships OpenAPI docs:

UI: HOME → REST-API Doc
URL: http://localhost:8000/api-docs/ (replace host/port as needed)

That document is authoritative for paths, payloads, and versions.

Scope

Compared with Maxx Control’s device REST API, this API targets the Maxx Remote project/server — operator-oriented control of the system Maxx Remote manages, not low-level single-device setup.

Volume Control

Mon, 01 Jan 0001 00:00:00 +0000

Channel Volume Control

Volume control is one of the most common operations. You can control individual channels or multiple channels at once.

Get Channel Volume

Retrieve the current volume setting for a specific channel:

curl -X 'GET' http://${IP}/rest-api/settings/channel/1/dsp/volume

{
 "value": -10.5
}

Set Single Channel Volume

Set the volume for a single channel. Volume range is -72.0 dB to +24.0 dB:

AES67 / SDP subscribe

Mon, 01 Jan 0001 00:00:00 +0000

Subscribe an amplifier channel DSP patch to an external AES67 / SDP audio source. This is the same path Maxx Control’s channel-input UI uses when you paste SDP or pick a discovered AES67 flow.

When to use

Use this when a third-party sender (PipeWire, another AES67 device, etc.) publishes an SDP session and you want a MAXX channel to receive that multicast/unicast RTP stream as its input source AES67 STREAM (source_id 25).

Maxx Control REST: Switch input patches

Mon, 01 Jan 0001 00:00:00 +0000

AES67 / SDP

To subscribe a channel to an AES67 / SDP stream (source_id 25), see AES67 / SDP subscribe.

Use the Maxx Control REST API to switch channel input patches (for example Dante slots) with a bulk PUT or per-channel calls. When switching between inputs, there are multiple approaches:

Changing the Input Patch itself

Example Configuration for CH1, CH2, CH4, CH7, switch between Dante Input 1-4 and Dante Input 21-24

Maxx Remote View API

Mon, 01 Jan 0001 00:00:00 +0000

The Maxx Remote View API exposes a saved VIEW as a standalone operator page — without the Maxx Remote editor chrome. Operator URLs use the /view/ path (also called the View API).

What is the Maxx Remote View API?

Use it when you want tablets or dedicated operator PCs to show only the mute / volume / meter widgets you placed in VIEW, not the full project editor.

How do I open a VIEW operator page at /view/?

In VIEW, create and SAVE a page.
Copy the operator Link from the editor toolbox.
Open URLs of the form:

http://<server>:8000/view/<view-name>

Amp enable

Mon, 01 Jan 0001 00:00:00 +0000

Power-enable a channel amplifier stage (distinct from mute):

PUT /settings/channel/{channel_id}/ampenable

curl -X PUT "http://${IP}/rest-api/settings/channel/1/ampenable" \
 -H "token: f4005bf8507999192162d989d5a60823" \
 -H "Content-Type: application/json" \
 -d '{"value": true}'

Use "value": false to disable. Multi-channel updates can go through PUT /settings/channel with ampenable on each object.

Group signal path

Mon, 01 Jan 0001 00:00:00 +0000

Goal / when to use

Embed or bookmark a SIG-PATH page for one room/group — useful on a monitoring wall.

URL pattern

Groups are addressed by their internal id (UUID), for example:

http://<server>:8000/group-signal-path/<group-uuid>

Example:

http://localhost:8000/group-signal-path/36875a19-8203-4647-9760-303ffd3c8f8f

Obtain the group id from your project/export or integrator tooling — it is not the display name.

Save / persist

Mon, 01 Jan 0001 00:00:00 +0000

Runtime changes are held until they are saved. Trigger a manual save with:

PUT /settings/save (token required; no JSON body)

curl -X PUT "http://${IP}/rest-api/settings/save" \
 -H "token: f4005bf8507999192162d989d5a60823"

Check save / autosave state with GET /status/save.

Note

The device may also autosave. Integrators that change many parameters in a burst should still call /settings/save when a persistent result is required (power cycle / reboot).

Third Party Plugins

Mon, 01 Jan 0001 00:00:00 +0000

These plugins use the device REST API to control one amplifier each. For multi-amp project control, use Maxx Remote instead.

API

Mon, 01 Jan 0001 00:00:00 +0000

Maxx Remote exposes a few user-facing integration surfaces. This section stays thin on purpose: the live OpenAPI document on a running system is the contract for REST calls.

Entry point	Typical use
REST API	Third-party control (media controllers, show control)
View API	Fullscreen operator pages at `/view/`
Group signal path	Scoped SIG-PATH page for one group

OpenAPI UI on a running host: http://localhost:8000/api-docs/ (also linked from HOME → REST-API Doc).

Loxone Maxx Control plugin

Mon, 01 Jan 0001 00:00:00 +0000

Loxone integrators can control one Innosonix amplifier via Maxx Control using the Loxone Library plugins and example templates. Install the add-ons into Loxone Config, point each instance at the amp IP (or hostname.local), and drive mute, volume, and status over the device REST API.

What is the Loxone Maxx Control plugin?

The Loxone Maxx Control integration is a set of .LxAddon plugins from the Loxone Library that talk to a single amplifier’s Maxx Control REST API. Instantiate a plugin once per physical device.

Q-SYS Maxx Control plugin

Mon, 01 Jan 0001 00:00:00 +0000

Q-SYS integrators can control one Innosonix amplifier via Maxx Control using the Innosonix Maxx Control plug-in for Q-SYS Designer. Add the plug-in to your design, enter the amp IP, and expose mute, volume, meters, and status to Q-SYS UCIs and logic.

What is the Q-SYS Maxx Control plugin?

Innosonix provides a plug-in that integrates Maxx Series amplifiers (Maxx Control) with the QSC Q-SYS ecosystem. Devices can then be controlled from Q-SYS Designer, Q-SYS compatible user-control interfaces, and GPIO logic on Q-SYS cores and peripherals.

Integrators on Innosonix Docs

Maxx Control REST: Set channel names

Get Channel Name

Set Channel Name

Maxx Control REST: Control device mute and volume

Device Mute

Get Device Mute State

Set Device Mute

Device Volume

Device Information

Getting Device Information

Get Device Information

Understanding the Response

Maxx Control REST: Enable or disable EQ

Enable EQ for Multiple Channels

Disable EQ for Multiple Channels

Mute Control

Channel Mute Control

Get Channel Mute State

Mute a Single Channel

Unmute a Single Channel

REST API

Base URL and transport

REST API

Goal / when to use

Where is the full reference?

Scope

Volume Control

Channel Volume Control

Get Channel Volume

Set Single Channel Volume

AES67 / SDP subscribe

When to use

Maxx Control REST: Switch input patches

Changing the Input Patch itself

Maxx Remote View API

What is the Maxx Remote View API?

How do I open a VIEW operator page at /view/?

Amp enable

Group signal path

Goal / when to use

URL pattern

Related

Save / persist

Third Party Plugins

API

Loxone Maxx Control plugin

What is the Loxone Maxx Control plugin?

Q-SYS Maxx Control plugin

What is the Q-SYS Maxx Control plugin?