Exchange a Social Login Token for an Access Token

Endpoint URL: {socialLoginDomain} /signin/oauth_token

Description

This endpoint exchanges a Social Identity Provider OAuth token, or an IDP token for an Identity Cloud Social Login token, which is needed for social registration and login calls using Akamai's OAuth endpoints. This endpoint would be used if you are implementing a solution that authenticates users with an Identity Provider directly and not using a Social Login application.

Respects the API Client Allow List: No

Accepted Content-types

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

Authentication

No authentication is required to call the /signin/oauth_token endpoint.

Base URL

The base URL for this endpoint is your application domain; for example:

https://educationcenter.rpxnow.com

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

Example Request

This command exchanges a sign-in token obtained from Facebook for an Identity Cloud social login token. The social login token can then be used for social registration and login calls by using Akamai's OAuth endpoints.

curl -X POST \
 'https://greg-stemp.rpxnow.com/signin/oauth_token' \
 -H 'Content-Type: application/json' \
 -d '{
   "provider":"facebook",
   "token": "EAAV6lsQIR0gBAItAtDeUZBbsFiHuTxhLaHLw9TqGDsXK6GQodDfgKXcCkxkZCZBxLKsxsWgV0iZATVAzx2RGlsOIFDIals3ZCblCEJn25pTj4Lk7XZCCEweKkHfHZBPP8B75dXc1BagGjNy8ZBpyObZB8FZCWSK0AAWevv15aEh85lTwZZDD"
  }'

Running this command in Postman

Example Response


{
  "stat":"ok",
  "token":"e96213b7bfddd1884b91544a11b5d5be52316590"
}

Example Request: Sign In with Apple

This command exchanges a sign-in token obtained from Sign In with Apple for an Identity Cloud social login token. Note that Sign In with Apple requires you to use the id_token parameter instead of the token parameter.

curl -X POST \
 'https://greg-stemp.rpxnow.com/signin/oauth_token' \
 -H 'Content-Type: application/json' \
 -d '{
   "provider":"apple",
   "id_token": "eyJraWQiOiJBSURPUEsxIiwiYWxnIjoiUlMyNTYifQ.eyJpc3MiOiJodHRwczovL2FwcIFDIals3ZCblCEJn25pTF90aW1lIjoxNTc5NzMyNzU2fQ.J-uEzGb36-o_kQNPuYz8Q_1GP0RGQpjebrmrDZlwA86n859LuXpUvIrDiwPzAHanilCFPergm769XU3xqmb6fHxAdzRNAge3fi5j5YY66N3yjpzGQ2L2B-NcGb56XEPGz"
  }'

Running this command in Postman

Example Response


{
  "stat":"ok",
  "token":"db2778db7b59a03d045b1707dd85ae6fc726eafb"
}

Request Parameter

These items are used in the BODY parameter of your API call:

Parameter	Type	Required	Description
token	string	Yes	IDP token from Facebook or Twitter.
provider	string	Yes	Social identity provider. Allowed values are: facebook twitter googleplus apple Note that, despite the name, the provider parameter does not reference any Google+ endpoints or scopes; the Akamai Identity Cloud no longer supports Google+. Instead, all Google social logins are made through Google Sign-In. The name googleplus has been retained for backwards compatibility.
token-secret	string		Required when using Twitter as the social login identity provider.
id_token	string		Required when using Sign In with Apple. Set the value of the id_token parameter to the value of the token returned from your Sign In with Apple app.

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.