Instagram supports OAuth authentication only.
To allow users to connect through the provider, complete the tasks below:
Connect a Facebook Page to an Instagram account.
Create and register the provider as an app with Instagram.
Submit your app for Facebook's review.
To access Instagram data, users need a role on a page that is associated with an Instagram account. Any user with a role on the page has access.
To connect a page and an Instagram account, log into Facebook and from your Page's settings, click Instagram, and log into your Instagram account. If your account is not an Instagram Business Account, follow the prompts to set up a business profile.
Register an app to obtain the values for the OAuthClientId and OAuthClientSecret properties. The OAuth client credentials authenticate the provider to Facebook.
Log into Facebook and navigate to https://developers.facebook.com/apps.
Create a new app and click Settings > Basic. The OAuthClientId is the App Id displayed. The OAuthClientSecret is the App Secret.
Click Add Platform and select Website. Enter a Site URL. This value is not used in authentication.
Add the Facebook Login Product
Follow these steps to configure the OAuth redirect URI.
Go to your app settings and add the Facebook Login product from the "Products" section.
In the product settings, define the OAuth redirect URI.
If you are building a desktop application, set the redirect URI to https://localhost:33333/, or a similar https url.
If you are building a web application, set the redirect URI you want to be used as the callback URL that users return to with the token that verifies that they have granted your app access.
Add the Instagram API Product
Follow these steps to configure the Instagram API permissions your app requests:
Go to your app settings and add the Instagram product from the "Products" section.
Configure the permissions in the product settings. To access all the tables and views, include the following scopes:
instagram_basic
instagram_manage_comments
instagram_manage_insights
While you can still with an application without review, to go live and fully access Instagram content, you must submit your application for review and approval.
Click Manage for your application and on the Permissions tab click Start a Submission.
Select the use case that best describes your Instagram integration.
Fill in the form and wait for your application to be approved.
After setting the following, you are ready to connect:
InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
OAuthClientId (custom applications only): Set this to the client Id assigned when you registered your application.
OAuthClientSecret (custom applications only): Set this to the client secret assigned when you registered your application.
CallbackURL (custom application only): Set this to the redirect URI defined when you registered your application.
When you connect, the provider opens Instagram's OAuth endpoint in your default browser. Log in and grant permissions to the application. The provider then completes the OAuth process:
The provider obtains an access token from Instagram and uses it to request data.
The OAuth values are saved in the path specified in OAuthSettingsLocation. These values persist across connections.
The provider refreshes the access token automatically when it expires.
The LinkedIn CompanyId is a string of numbers, usually 6 to 9 digits long, that is unique to your company. You can find this ID in the URL of the search results page when you click on See All Jobs on your LinkedIn Page. The CompanyId is often required in queries for company data. While this may be set directly in the criteria of a query, the CompanyId may be set globally to avoid issues where the query is not so easily modified.
LinkedIn supports OAuth authentication only.
Log in to your LinkedIn developers dashboard and click Create New App. Enter information to be displayed to users when they are prompted to grant permissions to your application.
Select your application and select the following in Default Application Permissions: w_share, r_basicprofile, and rw_company_admin.
Set the RedirectURI:
For desktop applications, set the Redirect URI to http://localhost:33333 or a port number of your choice. When you connect must set the CallbackURL connection property to this exact URL.
For web applications, set the Redirect URI to a page on your Web app that you would like the user to be returned to after they have authorized your application.
For headless machines, set the Redirect URI to http://localhost:33333 or a port number of your choice.
The OAuthClientId and OAuthClientSecret are also displayed in the same page.
After setting the following, you are ready to connect:
InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
OAuthClientId (custom applications only): Set this to the client Id assigned when you registered your application.
OAuthClientSecret (custom applications only): Set this to the client secret assigned when you registered your application.
CallbackURL (custom application only): Set this to the redirect URI defined when you registered your application.
When you connect, the provider opens LinkedIn's OAuth endpoint in your default browser. Log in and grant permissions to the application. The provider then completes the OAuth process:
The provider obtains an access token from LinkedIn and uses it to request data.
Extracts the access token from the callback URL and authenticates requests.
Saves OAuth values in the path specified in OAuthSettingsLocation. These values persist across connections.
The provider refreshes the access token automatically when it expires.
The following are optional connection properties:
Target: Some Facebook tables can be filtered by a target. For example, to retrieve comments on a video, specify the Id of the video as the target. This property enables you to restrict the results of all queries in the connection to records that match the specified target. You can also specify this restriction per query with the Target column.
AggregateFormat: The provider returns some columns as a string aggregate. For example, the available likes data for an entity is returned in aggregate. By default, the provider returns aggregate columns in JSON. You can also return aggregates in XML.
Version: Set this property to the Facebook API version if you need to work with a different version than the default.
Facebook uses the OAuth standard to authenticate users.
In all OAuth flows, you must set AuthScheme to OAuth. The sections below assume that you have done so.
See Creating a Custom AzureAD App for information about creating custom applications.
InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
OAuthClientId: (custom applications only) Set this to the client Id in your application settings.
OAuthClientSecret: (custom applications only) Set this to the client secret in your application settings.
CallbackURL: Set this to the Redirect URL in your application settings.
Scope (optional): Set this if you need to customizie the permissions that the driver requests.
AuthenticateAsPage (optional): Set this to a page name or Id to make requests as a page. The page must be managed by the authenticated user.
When you connect the provider opens the OAuth endpoint in your default browser. Log in and grant permissions to the application. The provider then completes the OAuth process:
Extracts the access token from the callback URL.
Obtains a new access token when the old one expires.
Saves OAuth values in OAuthSettingsLocation. These values persist across connections.
The provider includes embedded OAuth credentials in order to connect to Twitter. You can connect without setting any connection properties for your user credentials. When you connect the provider opens the OAuth endpoint in your default browser. Log in and grant permissions to the application. The provider then completes the OAuth process.
All tables require authentication. You must use OAuth to authenticate with Twitter. OAuth requires the authenticating user to interact with Twitter using the browser.
You can follow the steps below to create a Twitter app and obtain the OAuth client credentials:
Log in to https://developer.twitter.com/en/portal/projects-and-apps. If you haven't already, sign up for a developer account.
To access the Twitter API v1.1, you need to Apply for additional access within the developer portal. You can read more about this in the Twitter API documentation.
Once you're on the Developer Portal, create a new Project. When you're done, you are redirected to create a new App. You can also go to the Project you just created and click Add App.
Set a name for the App and Twitter displays your keys and tokens. You should save these values somewhere since you need them later for authentication.
Go to the App settings. Under User authentication settings click Set up. Turn on the 'OAuth 1.0a' authentication.
Select Read and write and Direct message from the available App permissions.
Enter the website and other optional information to be displayed to users when they connect.
Set the Callback URL to http://localhost:33333/.
If you intend to communicate with Twitter only as the currently authenticated user, then you can obtain the OAuthAccessToken and OAuthAccessTokenSecret directly from the Developer Portal on Twitter. Navigate to your App and go to Keys and tokens. There, click Generate on the Access Token and Secret option. You can then connect by setting the OAuthAccessToken and OAuthAccessTokenSecret connection properties.
Otherwise, if you need to generate access tokens for other user accounts besides the one you used to create the app on Twitter, use the consumer key and consumer secret.
You can follow the steps below to obtain the OAuth client credentials:
Log in to https://developer.twitter.com/en/portal/projects-and-apps. If you haven't already, sign up for a developer account.
To access the Twitter API v1.1, you need to Apply for additional access within the developer portal. You can read more about this in the Twitter API documentation.
Once you're on the Developer Portal, create a new Project. When you're done, you are redirected to create a new App. You can also go to the Project you just created and click Add App.
Set a name for the App and Twitter displays your keys and tokens. You should save these values somewhere since you need them later for authentication.
Go to the App settings. Under User authentication settings click Set up. Turn on the 'OAuth 1.0a' authentication.
Select Read and write and Direct message from the available App permissions.
Enter the website and other optional information to be displayed to users when they connect.
Define the Callback URL setting.
If you are making a Web app, set the Callback URL to the URL you would like users to be returned to after they have granted your application privileges. If you are making a desktop application, set the Callback URL to http://localhost:33333/.
If you intend to communicate with Twitter only as the currently authenticated user, then you can obtain the OAuthAccessToken and OAuthAccessTokenSecret directly from the Developer Portal on Twitter. Navigate to your App and go to Keys and tokens. There, click Generate on the Access Token and Secret option. You can then connect by setting the OAuthAccessToken and OAuthAccessTokenSecret connection properties.
Otherwise, if you need to generate access tokens for other user accounts besides the one you used to create the app on Twitter, use the consumer key and consumer secret.