AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
We recommend that your client logs all failed requests and their responses (HTTP headers, and the xml body) to assist debugging. This is the error element's code attribute in the XML returned in the response body. The lfm error code (when the lfm status was "failed") further describes the cause of the error. The lfm status attribute of the lfm XML element returned in the response body.Last.fm signals the success or failure of a request by three different means: Return a response to the client indicating the outcome of the request.Update the user's Now Playing status with the track and client.Check that the request passes our filters.Once a request has been received by Last.fm the following sequence of events takes place on our side: The web service method for sending Now Playing information is track.updateNowPlaying.Īs with all our write web services, requests must be sent as HTTP POST requests to with form urlencoded parameters in the body of the request. Requests should be sent as soon as a user starts listening to a track. This API method call is optional for scrobbling clients, but recommended. This does not affect a user's charts, but will feature the current track on their profile page, along with an indication of what music player they're using. The "Now Playing" service lets a client notify Last.fm that a user has started listening to a track. Scrobbling 2.0 is not backwards compatible with the old Submissions Protocol 1.2.1 (which is deprecated). A client is anything that plays music, such as desktop music players, mobile apps, websites, etc.įor every track a user listens to the client should send a track.updateNowPlaying request and a track.scrobble request. Scrobbling is a way to send information about the music a user is listening to. This is a guide on how to send scrobbles to Last.fm.
0 Comments
Read More
Leave a Reply. |