Skip to main content
Authentication

Everything you need to know about authentications when using Plum APIs

Admin avatar
Written by Admin
Updated over a month ago

Authentication

All requests to the Rewards API must be authenticated. This section talks about how you can create and manage tokens.

Plum uses the standard OAuth 2.0 protocol and RESTful Rewards API for clients to integrate Plum’s vouchers into their environment.

Authentication URLs value

While getting started, you may use a Sandbox account in the staging environment. And once you've familiarized yourself with Plum APIs, you may migrate over to the production environment.

Client ID, Secret ID, and Token Creation

All requests to the Plum Rewards API must be authenticated.

Plum uses bearer authentication, where each request must include an HTTP header that includes your Client ID, Secret ID, and Access Token. The following guide explains how to generate your client ID, secret ID, and access tokens from the admin portal.

IP Whitelisting

Please share your list of IPs allowed to be whitelisted with your Implementation Manager.

IPs for the staging and production accounts are needed.

Did this answer your question?