A new Chrome Extension called FrontPage was recently created, utilizing the New York Times API.
The extension sends an AJAX request to the API and receives a JSON response. However, to make this possible, specific permissions need to be set in the manifest.json
file as follows:
...
"permissions": [ "https://api.nytimes.com/*" ],
...
If these permissions are not properly configured, the Extension may encounter a Cross Origin rejection error.
When users install the Extension from the Web Store, they are presented with a warning that states: "[The extension] Can access all your data on api.nytimes.com". Despite only retrieving public information from the API without storing any user data, this warning may seem excessive to users.
Is there a way to avoid displaying this warning to users when using an API in a Chrome Extension? Are there alternative approaches to integrating APIs into extensions without triggering such alerts?