Adds or updates an OAuth access_token for a user outside the usual login flow.

When a user logs in with an OAuth1 or OAuth2 Identity Provider, Janrain will request an OAuth token from the provider. This OAuth token is used when making subsequent API calls to the provider. The add_or_update_access_token call adds a token retrieved using a different method to Janrain.

Possible Use Cases:

  • If you are migrating an existing application to Social Login or have otherwise acquired an OAuth token for a user outside of Janrain, you may wish to pass that token to in in order to make Janrain RESTful API calls for that user.
  • Data is needed for a user that has never registered using Social Login before. The user's ID and access token are recorded, making it possible to use the get_user_data endpoint.

Only these identity providers support this call:

  • Facebook
  • RenRen
  • Soundcloud
  • Foursquare

Accepted Content-types

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

This endpoint includes the following methods:

  • POST


Example Request

curl -X POST \
    --data-urlencode apiKey=1234567891234567891234567891234567891234\
    --data-urlencode token=123456789123456789\
    --data-urlencode identifier=http://www.facebook.com/profile.php?id=123456789123456789123\
      Running this command in Postman

Example Response

  "stat": "ok"


This endpoint supports Basic authentication. 

How to Create an Authentication String

Base URL

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


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

Query Parameters

Parameter Type Required Description
apiKey string Yes Social Login API key. This key can be found on the Janrain Dashboard.
identifier string Yes Identifier associated with the social login identity provider. This value must be formatted as part of a URL; for example
token string Yes Access token for the user. Tokens must be requested from identity providers based on their API requirements.