API Keys

Overview

API keys let your own servers call UniSignIn, for example to push user data into UniSignIn from your CMS, CRM or subscription system.

Create an API key

1. Go to Connect > API Keys.
2. Create a key and copy its Secret Key.
3. Store the key on your server only. Never put it in page code or an app.

The list shows when each key was last used. Delete keys you no longer need.

Push user data

Create an import in Data Management > Data Exchange:

1. Set Exchange Type to Import Data and choose the source system.
2. Choose the field that identifies the user, e.g. email, and map your fields to UniSignIn profile fields.
3. Save it and copy the exchange ID.

Then send user data from your server:

curl -X POST https://secure.signinservice.com/api/v1/user/EXCHANGE_ID \
  -H "Authorization: Bearer SECRET_KEY" \
  -H "x-license: YOUR_LICENSE" \
  -H "Content-Type: application/json" \
  -d '[{"email": "[email protected]", "first_name": "Alex"}]'

Send one user or a list of up to 100 users per request. Users who don't exist yet are created when the identifier is email. The response shows how many users were updated and created:

{ "status": 1, "updated": 1, "created": 0 }

Use your own UniSignIn API domain if you have one, and the license of your project. For a complete setup with your own login system, see Connect Your Own Login System.

Related

• To read a logged-in user on your server, or log users in with your own system, use the SSO Token.
• To let other apps log in with UniSignIn accounts, see OAuth2 Server.