Nokia's Places API is a web service API that allows you to offer your application's users Nokia's Places service as available in Nokia Maps and other applications within the look & feel of your own application.
The Places service supports a variety of use cases that center around two major features:
> Place discovery â€“ Help users find the places relevant to them
> Place information retrieval â€“ Provide detailed information about places users are interested in
For place discovery, the Places API supports two different usage scenarios that you may select according to the requirements for your application:
> search â€“ find places that match search terms provided by the user
> explore â€“ guide users to relevant places nearby
The API follows the RESTful principles. It defines resources that represent the entry points for the supported use cases and uses hypermedia links to describe the application flow within a selected use case.
For example, discover is a Places API resource, representing all place discovery entry points. When you submit a GET request to the search subresource, you receive a response that contains a list of links to places or place resources, among other items. Each referenced place may have rich content associated with it including ratings, images, reviews, editorials, and owner content. It also contains references to other related places that allow your users to discover other places relevant or related to their original search.
The following is a list of historical changes that were made to this asset. Typically, once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change. As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset, we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb. If you spot an error in our data and believe that a record needs to be updated in some way, the ProgrammableWeb team would very much like to hear from you at email@example.com
So far, we don't have a record of any changes to this API