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

API version upgrades

Keep track of changes and upgrades to the Voucherify API.

Your API version controls the API and webhook behavior you see (e.g., what properties you see in responses, what parameters you’re permitted to send in requests, etc.). Your version is set the first time you make an API request. When we change the API in a backwards-incompatible way, we release a new dated version, but to avoid breaking your code, we don’t change your version until you’re ready to upgrade.

How can I upgrade my API?

If you’re running an older version, you’ll want to upgrade to take advantage of the latest and greatest API. For changing your API version you must send a request to Voucherify support team using email or contact page.

Moreover, to see what version you’re running and upgrade to the latest, you can go to Account Settings view which is visible in Voucherify Dashboard.

Changes which Voucherify considers to be backwards-compatible

  • Adding new API resources.
  • Adding new optional request parameters to existing API methods.
  • Adding new properties to existing API responses.
  • Changing the order of properties in existing API responses.
  • Changing the length or format of object IDs or other opaque strings.
  • Adding new event types. It means that your webhook listener should gracefully handle unfamiliar events types.

API changelog

Version
Description

v2017-04-05

  • Responses from the voucher and campaign listing methods were moved to the new object structure. Methods will now render specific properties for a total count and an array of objects.
  • Introduced validation for listing parameters: limit and page. A limit can range between 1 and 100 items.
  • Get voucher/campaign methods render validation rules related to the voucher object. They can be inherited from a campaign.
  • Created API method for getting a campaign identified by name.

v2017-04-20

Response from the voucher publish method was moved to the new object structure. Returned voucher details are wrapped by transaction object describing publication event:

{
  "id": "pub_whQzIndYoyZoqiLEKN0s04GK",
  "object": "publication",
  "created_at": "2017-04-20T13:18:01Z",
  "customer_id": "cust_mOjhGypfbqch0v3DpAA9LDXj",
  "tracking_id": "janusz",
  "channel": "API",
  "metadata": {
    "test":true
  },
  "voucher": {}
}