OAuth

If you’re a LoyaltyLion partner, you can authenticate with our API as an OAuth client. Our server implements the OAuth 2.0 specification.

Registering your OAuth app

Before you can authenticate with OAuth, you’ll need to register your app with LoyaltyLion. To register a new OAuth app with LoyaltyLion, please email partnersupport@loyaltylion.com with the following information:

• Your company/app name
• URL to your company/app
• Short description (max 150 characters) of your app
• Copy of your company logo or link to a press pack
• Your install URL, which must be https
  • Merchants who initiate installation from their LoyaltyLion account are sent here
  • It should require login / signup to your app
  • Once the merchant is authenticated with your app, it should redirect into the LoyaltyLion OAuth approval flow
• Your redirect URL, which must be https
  • We’ll redirect merchants here once they approve access for your app, for example: https://app.example.com/auth/loyaltylion
  • Landing on this page should initiate token exchange
• An actively monitored email address to receive important alerts such as webhook delivery failures to your app

Once we’ve approved your OAuth 2.0 app, we’ll provide you with a client id and secret. Your client secret must be kept private. If you believe it has been compromised, please contact us immediately.

Performing the OAuth 2.0 flow

Initiating OAuth 2.0 approval

To kick off the OAuth flow, start by sending the user to our authorize URL, https://app.loyaltylion.com/oauth/authorize, with the following parameters:

Example authorize URL:

# client_id: 317979793529
# scope: read_customers
# redirect_uri: https://api.example.com/auth/loyaltylion

https://app.loyaltylion.com/oauth/authorize?client_id=317979793529&scope=read_customers&redirect_uri=https%3A%2F%2Fapi.example.com%2Fauth%2Floyaltylion

When a user is redirected to the authorize URL, we’ll show them your app name, description and logo and ask them to approve the requested scopes.

Acquiring an access token

If they approve the request, we’ll redirect them to your redirect_uri including a code as query param you can swap for an access_token.

For example: https://app.example.com/auth/loyaltylion?code=fe53739dab6d76cc

To exchange the code for a permanent access token, your server should make a POST request with the code, your client id and your client secret.

# client_id: 317979793529
# client_secret: 97b0dc6dde30f189
# code: fe53739dab6d76cc

curl --request POST \
  --url 'https://app.loyaltylion.com/oauth/access-token' \
  --data 'client_id=317979793529&client_secret=97b0dc6dde30f189&code=fe53739dab6d76cc' \
  --include

If the exchange is successful, we’ll return a JSON response containing your permanent access token and a comma separated list of the approved scopes:

{
  "access_token": "e1c752f1b5cd8b743148a586e573b679",
  "scope": "read_customers"
}

Using the access token

Once you’ve received the access token, you can use it to make authenticated API requests allowed by the approved scopes. To do so, pass the access token using the bearer authentication scheme.

# access_token: e1c752f1b5cd8b743148a586e573b679

curl \
  --header 'Authorization: Bearer e1c752f1b5cd8b743148a586e573b679' \
  --header 'Content-Type: application/json' \
  --url 'https://api.loyaltylion.com/v2/customers'

Resource scopes

Scopes let you specify the type of access your app needs, and limit the capability of the associated access tokens. When making your initial request to our authorize URL, you should pass through the scopes needed by your app as a comma separated list.

Our webhooks API is available to all access tokens, but you can only create webhooks for resources permitted by the token’s scope.