APIs used in POWR Apps

We use APIs in a bunch of our Apps. Very often, when you see an issue with data displayed incorrectly in those Apps, its due to an issue with the API. Here is an overview of all APIs we use and what issues you can expect to see in the Apps using them:

App

API

Common issues

Countdown Timer Microblog Plan Comparison Slider

PayPal API

Various limitations, mostly unsupported currencies and end-user requiring PayPal account

eCommerce

PayPal API

Various limitations, mostly unsupported currencies and end-user requiring PayPal account.

Facebook Feed

Facebook API

Cannot display pages with restrictions on them. Cannot display Events.

File Embed

Google Viewer

File doesn't display if too large or if file name has spaces or umlauts in it.

Form Builder

PayPal API, Mailchimp

Map

Google Maps

Location can't be found (because address needs to be entered exactly as displayed in Google location listing)

Music Player

Soundcloud

Instagram Feed

Instagram API

Weather

openweathermap.org

The weather forecast isn't accurate! (Well, we don't have any control over that) My location cannot be found! (Ask user to submit a request to OpenWeatherMap)

Apps where we don't use an API

... even though you might assume we do:

Twitter Feed: We no longer support the Twitter API after the huge charge they implemented recently.
Pinterest Feed: Pinterest doesn't have an official API. We use a web scraper. *EDIT* Aigul says we are totally using (and have always been using) the official API 🤔

Refresh rates are based on app creation date. You can look up the timestamp for when an app was created in the User Journey tab of TSH.

APIs used in POWR Apps

Apps where we don't use an API

Social Feed refresh rates: