Bose SoundTouch Toolkit

Documentation for controlling and preserving Bose SoundTouch devices

View the Project on GitHub gesellix/Bose-SoundTouch

SoundTouch supportedURLs Endpoint Analysis

This document provides a comprehensive analysis of the /supportedURLs endpoint response from real Bose SoundTouch devices and compares it with our current implementation.

Discovery Summary

Test Devices:

Key Findings:

Endpoint Categories

✅ Fully Implemented (Core Functionality)

Device Information (5/5):

Playback Control (3/3):

Volume & Audio (4/4):

Source Management (2/2):

Preset Management (1/2):

Zone/Multiroom (4/4):

Clock & Display (2/2):

Advanced Audio (3/3):

System Info (3/3):

🔶 Partially Implemented/Different Approach

Zone Management:

❌ Not Yet Implemented (High Priority)

Enhanced Playback Control:

Source Enhancement:

Music Services Integration:

Enhanced Presets:

Station/Radio Management:

❌ Not Yet Implemented (Medium Priority)

System Configuration:

Network & Connectivity:

Bluetooth Enhancement:

Content Discovery:

❌ Not Yet Implemented (Low Priority)

Pairing & Setup:

Software Updates:

System Utilities:

Internal/Advanced:

Product Management:

Cloud Integration (EOL May 2026):

Enhanced DSP (Device Dependent):

Implementation Recommendations

Phase 1: High-Value User Features

  1. Enhanced Source Selection - /selectLast* endpoints for better UX
  2. Preset Management - /storePreset, /removePreset, /selectPreset
  3. Station Management - Radio/streaming station operations
  4. Music Service Integration - Account management endpoints

Phase 2: System Enhancement

  1. Power Management - Standby and power saving controls
  2. Network Management - WiFi profile and radio control
  3. Content Discovery - Search and navigation capabilities
  4. Bluetooth Enhancement - Pairing management

Phase 3: Advanced Features

  1. System Diagnostics - Network stats, introspection
  2. Update Management - Software update control
  3. Notification System - Notification management
  4. Advanced Setup - Pairing and configuration tools

Notes

  1. Device Consistency: Both test devices expose identical endpoint lists, suggesting consistent firmware behavior across SoundTouch models.

  2. Official vs. Real: The device exposes 84 additional endpoints beyond the 19 documented in the official API v1.0, indicating significant undocumented functionality.

  3. Cloud Dependency: Some endpoints (especially /marge*) may become non-functional after the May 2026 SoundTouch cloud EOL.

  4. Implementation Strategy: Focus on user-facing functionality first, then system management, finally internal/diagnostic features.

  5. Testing Required: Each new endpoint implementation should be tested against real hardware to verify functionality and response formats.

  6. Documentation Gap: Many endpoints lack official documentation, requiring reverse engineering through testing.

Raw Device Response

Device Count: 103 unique endpoints Response Format: XML with URL location attributes Common Pattern: Most endpoints support both GET (query) and POST (modify) operations

Example Response Structure:

<?xml version="1.0" encoding="UTF-8" ?>
<supportedURLs deviceID="08DF1F0BA325">
    <URL location="/info" />
    <URL location="/capabilities" />
    <!-- ... 101 additional endpoints ... -->
</supportedURLs>

This analysis provides a roadmap for expanding the Go library’s API coverage from 34% to potentially 100% of available device functionality.