Sonos uses getLastUpdate to poll your service for changes. The message has no input parameters. When content on your service changes, you should change the values in your response. The getLastUpdate response has two different associated values, a catalog value and a favorites value. Both should return a string that indicates the current version of the resource in question for your service. Each time your service changes the string, change it to a new value that is never reused. See Synchronize your service for details.

Request parameters



autoRefreshEnabledBoolean(Optional) Enables the ability to disable automatic refresh of browse containers. Default is true. When set to false, the Sonos app will not call getMetadata on a container if the catalog or favorites value has changed. Instead, a getMetadata request will be issued only when the user does any of the following:

- Browses into a container.
- Browses out of a container.
- Scrolls to the point where the Sonos app needs to request further rows.
catalogstring(Optional) A token that represents the current version of your global catalog. This should include all of the content that is not updated by users. For example, lists of albums and artists. You should change the catalog value whenever you update your global catalog, such as during a daily content push.
favoritesstring(Optional) A token that represents user-specific content. This can include user likes, playlists, and the user's personal library. It can also include content that changes with greater regularity than the catalog, such as recommendations. This can include content that users can update on Sonos apps or on the native app for your service.
pollIntervalint(Optional) The length of time in seconds that the Sonos app should wait before polling the service with getLastUpdate again. This can be from 30 to 3600 seconds. If the value is null or under the minimum of 30 seconds, the Sonos app uses the value from the version manager form. If over, the app uses 3600 seconds. See Submit your service for details about the version manager.

Change the favorites value every time a user updates content

You should change the favorites value every time a user updates content, such as when a user creates a playlist, deletes a playlist, adds a track to their favorites, removes a track from their favorites, or performs any playlist editing function. The following occurs when the user performs one of these types of operations:

  1. The Sonos app sends a getLastUpdate request to your service.
  2. Your service sends back the current value for favorites.
  3. A user performs an action on their Sonos app that sends a message to your service, such as a REST request to add a favorite. See Add favorites for details.
  4. Your service responds to this request with a success response.
  5. After receiving your response, the Sonos app sends a getLastUpdate message to your service.
  6. You should respond with a new favorites value.
  7. This new favorites value triggers the Sonos app to refresh its user interface with a subsequent getMetadata request.
  8. Your getMetadata response will cause the changes to favorites to be reflected immediately on the specific Sonos app used.

Here's a sequence diagram of what happens on a Sonos app when someone adds a new favorite:

Sonos apps send getLastUpdate requests at defined intervals

The Sonos app will also send a getLastUpdate message at your defined polling interval to pick up other changes to user-generated content or your entire catalog. The user could change user-generated content outside of the Sonos app on your website or mobile app, or on a different Sonos app within the same Sonos system. Your global catalog changes when you push new content to all users.

If either the catalog or favorites string value has changed, Sonos apps refresh their copies of the data for that resource. When these values change, this invalidates the caches on Sonos apps and allows the user interface to reflect the changes. A Sonos app only sends the periodic getLastUpdate message to your service whenever a user is actively browsing your service or playing content from your service.

Keep in mind, this message is Sonos app-specific, so different Sonos apps attached to the same Sonos system may call getLastUpdate at different times. The timing depends on when the user started interacting with your service. For example, if a family member favorites a track on your music service using the Sonos app on their Android phone, someone else in the household who is using the iOS Sonos app will see that change only after their Sonos app makes its periodic getLastUpdate call.

If your server cluster processes getLastUpdate or getMetadata messages for a single Sonos app during a single user session, it is essential that all servers that the Sonos app might hit synchronously reflect the same up-to-date catalog and favorites values, and return consistent values for getMetadata. Otherwise, the user interface on the Sonos app may fail to update or update continuously at each polling interval. For this reason, it may be preferable to associate a given user session to a particular server for the duration of that session.

Sample request

<soap:Envelope xmlns:soap="">
   <getLastUpdate xmlns="">

Sample response

<soap:Envelope xmlns:soap="">
    <getLastUpdateResponse xmlns="">