Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 114 Next »


API stands for Application Program Interface, and is a set of routines, protocols, and tools for building software applications.

We released our APIs to the public so that you can integrate your systems with Vibes' system in near real-time.

Similar to the ability of the Vibes Mobile Engagement Platform to control Mobile Database and Campaign Manager, its APIs let a customer or partner integrate their software with Mobile Database and Campaign Manager. 

You can integrate with Vibes Mobile Database to store your People, Participants, and Subscribers. You can also use APIs to integrate with Vibes Acquisition Manager and Wallet Manager campaigns.

Vibes encourages you to use real-time integration tools whenever possible.

API Call Structure

The call structure of the APIs is as follows:

  • Method: HTTP is the format used to enable communication between clients (like Web browsers) and servers. The most common methods are GET, POST, PUT and DELETE.
    For more information on HTTP, see: HTTP Specification.
  • URL: The Web address. The URL host is the Vibes public API site.
  • Header: A unit of information that contains information about the file. Vibes APIs use a JSON file.
  • Body: Represents the body of the request or response and allows you to declare what the content type is and how it should be handled.

API Versions

There are currently two versions of the APIs available. You can see what version you are using by looking at the API header.

X-API-Version: 1

Topics in this Section

API Version 1

This is the default version. It does not accept the international format, E.164 phone numbers.

Note: If you are using Version 1, you cannot use the E.164 format. If you do use it, you will get an error returned.

API Version 2

To fully serve its international customers, Vibes released Version 2 of the Vibes Mobile Engagement Platform APIs in 2016 to include support for international E.164 phone numbers.

Example API Version 1

Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==

Example API Version 2 (E.164 MDN Format)

Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==

REST API Tree URI Structure




  • No labels