List Your Social Login Application Settings

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

Description

Returns the following application properties:

privacyPolicy — URL sent with requests for registration data and displayed by the identity provider as a link to the user.
favicon — URL of your favicon, which can be displayed by some identity providers during authentication.
domainRedirect — Available for enterprise level apps and for apps owned by Akamai Identity Cloud partners. A URL redirect destination for users visiting your sign-in URL (such as, http://janrain-docs.rpxnow.com).
oneTimeUseTokens — Allows tokens for the auth_info API call to only be used once.
googleProfileUrl — Returns a user's globally-unique Google profile URL as the identifier element in the auth_info API call response. This is returned instead of the OpenID URL.

Respects the API Client Allow List: No

Authentication

This endpoint uses your social login API key for authentication. This key can be found on the Settings page of the Social Login Dashboard.

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 social login application settings for the application 1234567891234567891234567891234567891234.


curl -X POST \
  --data-urlencode apiKey=1234567891234567891234567891234567891234\
  https://janrain-docs.rpxnow.com/api/v2/get_app_settings

Running this command in Postman

Example Response


{
  "stat": "ok",
  "privacyPolicy": null,
  "favicon": null,
  "domainRedirect": null,
  "oneTimeUseTokens": true,
  "googleProfileUrl": true
}

Query Parameters

Parameter	Type	Required	Description
apiKey	string	Yes	Social Login API key. This key can be found on the Social Login Dashboard.

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.