Skip to main content
Records that your integration has consumed the current state of a playlist. No request body is needed — all data is captured server-side: your token identity, the playlist state at the time of the call, and the server timestamp. Every call appends a new entry to the audit log. Repeated or retried calls are always safe.

Request

No request body.

Path Parameters

Response

204 No Content — no response body.

Error Responses

The 404 response covers both “playlist not found” and “playlist belongs to another company.” This is intentional — the API does not reveal whether a playlist ID exists if your token cannot access it.

What gets recorded

Each successful call inserts one row into the sync audit log: The playlistSongsUpdatedAt snapshot is the key audit signal. It lets you (and Musique ops) answer: was the partner’s copy of the playlist current at the time they synced?

Usage pattern

Call this endpoint after you have successfully fetched and applied the playlist from Get Playlist.