The Voucherify Developer Hub

Welcome to the Voucherify developer hub. You'll find comprehensive guides and documentation to help you start working with Voucherify as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started

Authentication

Flows and protocol

We use two pairs of keys – one for server applications (back-end) and one for publicly available clients (mobile applications and web apps).

Voucherify uses OAuth 2.0 as an authentication protocol for both. It is published under the RFC 6749.

Application authentication

In order to get access to the Voucherify API, a client application needs to pass Application ID and Application Secret Key. You can get (and reset) these tokens in the Project settings view of Voucherify's user interface.

A generated pair of Application ID and Application Secret Key must be attached to every HTTP request as properly named custom headers: X-App-Id, X-App-Token.

X-App-Id: 2f7075c7-201d-471f-a249-34c968092e70
X-App-Token: 7ccb680d-107e-45bd-8466-1f15048e34f4

Most likely you won't need to send the token manually. We provide a growing number of SDKs that know how to handle it, so no extra code is needed.

❗️

Security threat

It is essential that you secure your tokens and not expose it to others. Treat it as your application's password for Voucherify.

Client-side authentication

The second authentication mechanism uses publishable keys. It's meant to be used by the public (web and mobile) clients to access a subset of the API. See voucherify.js as an example.

🚧

Domain whitelist

Remember to whitelist your domain/mobile app origin in the Client-side Settings to allow client-side connections. See the picture below

Updated 5 days ago

Authentication


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.