Generally speaking, you will send a method parameter expressed as 'package.method' along with method specific arguments to the root URL. The API supports multiple transport formats but will respond in Last.fm idiom xml by default.
Note:
Please use an identifiable User-Agent header on all requests. This helps our logging and reduces the risk of you getting banned.
Be reasonable in your usage of the API and ensure you don't make an excessive number of calls as that can impact the reliability of the service to you and other users. We encourage best practice implementation, for example, if you're making a web application, try not to hit the API on page load. Your account may be suspended if your application is continuously making several calls per second or if you’re making excessive calls. See our API Terms of Service for more information on limits.
If you are planning to use our API for commercial purposes, please contact us via email at partners@last.fm.
We assume that you are using an RFC 3986-compliant HTTP client to access the web services. In particular, pay attention to your url encoding. This will not be an issue for 99% of developers.
The authentication protocol allows you to perform actions on user accounts in a manner that is secure for Last.fm users. All write services require authentication.
We encourage services that use the Last.fm API to build-in scrobbling natively into their applications (where applicable, and particularly for media players), to allow users to send listening data in to their Last.fm user profiles. This can be done through our Scrobbling API.
Join the Last.fm Support Forums for information about new Web Services, access to beta API's, provide feedback and discuss development with other developers.
