The Social API is unique among Identity Cloud APIs in that it doesn’t require a standard authentication method such as basic authentication or token-based authentication. In fact, for most operations no authentication or authorization header is used at all. For example, if you’re using Postman, your Authorization tab will look like this:
Instead of a standard authentication method, the Social API requires you to include your social login API key as an x-www-form-urlencoded response body. In Postman, that looks similar to like this:
If you’re using Curl, your API call might look like the following:
curl -L -X POST 'https://greg-stemp.rpxnow.com/api/v2/get_domain_patterns' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'apiKey=ut75nh71f79a416002bpo8hqa7375bffb6000o13'
If you don’t know your API key you can find the value in Console. Just go to the Manage Application page and look for the rpx_key setting:
The value is also available from the Social Login Dashboard. To find it, open the dashboard, click the Manage Settings icon, then look for the API Key (Secret) property:
