Full backend implementation for integrating with the SONOS platform. Fully operational and tested SMAPI (Sonos Music API) Java server and Cloud Queue.

Long Description

＜p＞＜span style="background-color: rgb(249, 250, 251); color: rgb(55, 65, 81);"＞Fully functional code and support available for listing your music service on Sonos. ＜​/​span＞＜​/​p＞＜p＞＜br＞＜​/​p＞＜p＞For content and user management, Sonos platform uses Sonos Music API (SMAPI), and, for music playback (content integrations only), it uses Sonos Cloud Queue API (CQ).＜​/​p＞＜ol＞＜li＞The SMAPI Java server implements Sonos Music API, which enables Sonos users to access their own personal accounts on your service using Sonos apps and players.＜​/​li＞＜li＞The CQ NodeJS server implements Sonos Cloud Queue API, which provisions the Sonos players with windows of track URLs to play.＜​/​li＞＜​/​ol＞＜p＞＜br＞＜​/​p＞＜p＞Together, these 2 servers cover all the external network calls performed by Sonos (apps and players).＜​/​p＞＜p＞                                SMAPI server covers the following key requirements:＜​/​p＞＜p＞                                - implements getMetadata & getExtendedMetadata SOAP methods to add your content to Sonos＜​/​p＞＜p＞                                - implements getMediaURI & getMediaMetadata SOAP methods to playback your content on Sonos＜​/​p＞＜p＞                                - implements getLastUpdate SOAP method to synchronize and update your content for Sonos users＜​/​p＞＜p＞                                - handles pagination for large lists of content＜​/​p＞＜p＞                                - returns defined errors as expected＜​/​p＞＜p＞                                - uses Transport Layer Security (TLS)＜​/​p＞＜p＞                                - allows traffic from the Prod US & Prod EU IP addresses (whitelists them and removes any rate limiting for them)＜​/​p＞＜p＞                                CQ server handles these four endpoints:＜​/​p＞＜p＞                                - ​/​context - Players request the playback context to get information about the playback conditions, such as the container type, metadata, versions, playback policies, and reporting options. For example, the container type could be a program on a radio station or a playlist.＜​/​p＞＜p＞                                - ​/​itemWindow - Players request a window of tracks in your cloud queue by specifying the itemId of a track in the cloud queue, the previousWindowSize (or the number of tracks before a specified track), and the upcomingWindowSize (the number of tracks after a specified track) to be returned. This also indicates the playback policies for individual items in the cloud queue. Optionally, the player can use this API to obtain a new access token in the response from your CQ server.＜​/​p＞＜p＞                                - ​/​timePlayed - Used by players to report how long a track was played and the time since it was last played. This notifies the CQ server via an HTTP POST when a track finishes playing. The payload includes the total playback duration, including any scrubbing and seeking within the track, as well as a signal whether the track ended due to a skip operation or not. Players only send reports when a track has played for more than one second.＜​/​p＞＜p＞                                - ​/​version - Your cloud queue has two strings, contextVersion and queueVersion, to signal changes in the cloud data. Each time the list of tracks, metadata, or skip enforcement data changes, you must change one of these version identifiers. The Sonos player is responsible for periodically polling this value to detect changes in the cloud queue track list, context metadata, or skip limits.＜​/​p＞

Software Usage Boundaries (known usage or performance limitation)

Requires user authentication and authorization. Ref: https://docs.sonos.com/docs/add-app-authentication#tag/playback/operation/Playback-LoadContent-GroupId Support is available on this matter.