List Your Configured Social Login Providers

Endpoint URL: {socialLoginDomain} /api/v2/providers

Description

Returns a list of configured sign-in or social providers configured for an application.

Respects the API Client Allow List: No

Authentication

This endpoint does not require authentication.

Accepted Content-types

application/x-www-form-urlencoded
multipart/form-data

Base URL

The base URL for this endpoint is your application domain followed by /api/v2; for example:

https://educationcenter.rpxnow.com/api/v2

You can find your application domain in the Social Login (Engage Dashboard) on the Settings page:

Example Request

This command returns information about the social login identity providers available for use with the application that uses the URL https://janrain-docs.rpxnow.com.


curl -X POST \
  https://janrain-docs.rpxnow.com/api/v2/providers

Running this command in Postman

Example Response


{
  "stat": "ok",
  "signin": [
    "aol",
    "facebook",
    "foursquare",
    "google",
    "linkedin",
    "live_id",
    "mixi",
    "openid",
    "orkut",
    "paypal",
    "salesforce",
    "sinaweibo",
    "twitter",
    "yahoo"
  ],
  "social": [],
  "shareWidget": {
    "share": [
      "email",
      "facebook",
      "linkedin",
      "myspace",
      "twitter",
      "yahoo"
    ],
    "email": []
  }
}

Responses

200 OK

Field	Type	Description
signin	dictionary	A list of configured sign-in provider names for the application.
social	dictionary	A list of configured social provider names for the application.
share	dictionary	A list of configured sharing providers. [Note: Sharing providers are no longer supported.]
email	dictionary	A list of configured sharing direct share providers. [Note: Sharing providers are no longer supported.]
callback	dictionary	Specifies the return of a JSONP-formatted response. The format parameter will be ignored if callback is present.

How to Create an Authentication String

To create an authentication string, combine your API client ID, a colon (:), and your client secret into a single value. For example, if your client ID is abcdefg and your client secret is hijklmnop, that value would look like this:

abcdefg:hijklmnop

Next, take the string and base64 encode it. For example, on a Mac, you can base encode the string using this command:

echo -n "abcdefg:hijklmnop" | base64

If you’re running Microsoft Windows, you can encode the string by using a Windows PowerShell command similar to this:

[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("abcdefg:hijklmn"))

The resulting value (e.g., YWJjZGVmZzpoaWprbG1ub3A=) should be used in your authentication header.

If you are making API calls using Postman, select Basic Auth as your identification type, then use the client ID as the username and the client secret as the password.

Before you actually try your authentication string, make sure that your API client has the all the permissions (for example, the right to read user profile information) needed to complete the API call.