Pinterest calls itself a "virtual pinboard," allowing users to select photos from web pages to share with their friends. This process, called pinning, helps users collect ideas, recipes, inspiration or anything that can be found in a photo on a web page.
The Pinterest API provides developers access to an authenticated user's pinboards and pins. The API provides detailed user data, as well as the home feed for a user, pins, likes, following, followers and the ability to unfollow. Developers can also access information about specific boards and pins, including creating boards, adding pins, categories and adding/removing likes.
The API allows businesses to integrate with Pinterest's social media platform in an effort engage with customers. With the APIs, developers can access a site's top repins, most recent pins, related pins, most clicked through pins and pins resulting from specific search terms.
The API makes its data available via JSON only, with requests also wrapped as JSON. Though the official documentation has been removed, we've included a cache of the page, as the API still appears to be supported.
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