Instagram plugin
What is Instagram?
Instagram is a popular social media platform focused on photo and video sharing. Users can post content, follow other accounts, and engage with a wide range of visual media. It's particularly popular for its filters and stories feature. Instagram is owned by Facebook's parent company Meta.
First, open the Install new plugins screen in the Bubble editor.
To find this plugin, search for Instagram. Optionally, you can check the Login service checkbox to further filter the results. You can also scroll to the bottom of the filters list, under Built by and select Official to single out official plugins.
Check that the Bubble logo is visible in the bottom-right, and then click Install.
Setting up and configuring the Instagram API
The Instagram API follows a common pattern of requiring two different keys to authenticate your app.
App ID: The App ID (also referred to as the API Key in some contexts) is essentially the public identifier for your app. Think of it like the name tag your app wears when it talks to Instagram. In this context, it's not to be confused with your secret access token: In fact, the Client ID doesn't need to be kept secret.
App Secret (access token): The Secret Key, on the other hand, is like a password. It's used to secure communication between your app and Instagram's servers. Exposure of the Secret Key can lead to security risks, unlike the App ID.
Setting up the Instagram plugin
After installing the plugin, you'll find it in your list of installed plugins and can click it to access its settings:
Actions, elements and data sources
To see the plugin's actions and data sources, as well as their properties, please see the core reference article below:
Reference: Instagram
FAQ: Instagram Graph API plugin
What should I do if I accidentally expose my App ID?
The App ID is a public identifier, and does not need to be replaced if it's exposed.
What should I do if I accidentally expose my secret key?
The secret key should be kept securely private, as exposure can lead to security risks. We strongly recommend revoking the exposed key and creating a new one immediately. Remember to deploy the changes in your app to Live after replacing the secret key.
Last updated