Walgreens Continues Developer-Focused Strategy with Two More APIs

Walgreens continues to expand its API strategy with two new APIs: the Store Locator API and the Digital Offers API. The Store Locator API allows partners to retrieve realtime, dynamic store location information about over 8,200 store locations. The Digital Offers API enables developers to integrate Walgreens coupons and offerings directly within third party apps. Both APIs remain in beta for the time being, but Documentation is publicly available.

Both APIs were originally developed and used to power the Walgreens mobile app, and the company decided to open the services to third parties. This strategy remains in line with how Walgreens has launched previous APIs to the developer community. Walgreens continues to shine as an example of a traditional, brick and mortar shop that constantly transforms itself through recruiting a developer community and empowering the community with more and more API offerings. For an overview of Walgreens' API portfolio, check out ProgrammableWeb's directory

The basic functionality of the Store Locator API creates an array of the 10 stores nearest the search location. However, Walgreens offers over 35 additional filters to refine returned results. Filter examples include locations with  drive-thru pharmacies, healthcare clinics, beer and wine sales, and many more. The Digital Offers API allows users to "clip" coupons to a loyalty card within an app. Associated savings are automatically applied at checkout. For more information, check out the APIs site.

Walgreens Developer Evangelist, Drew Schweinfurth, told Tech Crunch, "For 2016, we want to focus on looking at extending services that help developers make innovative applications." Since the launch of its first public-facing API in 2012, Walgreens has demonstrated an ongoing dedication to the developer community. We have come to expect such news from Walgreens and are eager to hear of similar news to come. 

Be sure to read the next API Strategy article: Why Your API's End-Usage Context Matters To Great Developer Experiences