Skip to content
Java based SDK for the API
Branch: master
Clone or download
sanjeevmandalapu How to reach out to us?
In case of any errors, please reach out via an Issue or fixes via PRs
Latest commit 99394df Mar 15, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
src Handling API Gateway Usage Limits Mar 15, 2019
.classpath Refactored the SDK into resource implementations. Added workspaces impl. Dec 26, 2014
.gitignore removed .DS_Store files Dec 26, 2014
.project reorganised project Sep 7, 2014
.travis.yml reorganised project Sep 7, 2014
LICENSE.txt added License Sep 7, 2014 How to reach out to us? Mar 15, 2019
pom.xml released 2.3.0 to support regional gateway endpoints Nov 23, 2018

Whispir's SDK for Java

Whispir's SDK allows Java Developers to get up and running with Whispir's API quickly.

Follow the instructions below to include the dependencies in your project.

If you've got any questions feel free to raise a Issue or fix an issue using the Pull requests

Installing with Maven

Users can easily include the Whispir dependency in their projects using Maven.

The dependency information is as follows:


See the examples section below for usage instructions.

Building/Installing the SDK from Source

Whispir's SDK is built using Maven. To create the JAR files, simply execute the install maven target (skip tests unless you want to add the static parameters in the tests file first).

mvn clean install -DskipTests=true

This will produce two JAR fies:


The JAR with dependencies should be used as a standalone import into any project.

If you are using other Apache HTTP Client libraries, the WhispirSDK.jar may suit your project better, so import that with your other HTTP Client libraries.

Note, you will need GPG installed to sign the libraries. This is included by default within the pom.xml file.

If you want to build from source but don't want to install gpg, then remove the following code from line 59 in the pom.xml:



The API can perform three activities at the moment:

  • Sending messages
  • Retrieving Workspaces
  • Sending scenarios

These are described below:

package com.whispir.sdk.examples;

import java.util.Map;
import java.util.TreeMap;

import com.whispir.sdk.WhispirEndPoints;
import com.whispir.sdk.WhispirResponse;
import com.whispir.sdk.WhispirSDK;
import com.whispir.sdk.exceptions.WhispirSDKException;

public class SDKExample {

  //APIKEY, Username and Password available from
  public static final String API_KEY = "...";
  public static final String USERNAME = "...";
  public static final String PASSWORD = "...";
  public static final WhispirEndPoints APIENDPOINT = WhispirEndPoints.AU;

  public static void main(String[] args) {
    try {

      // INIT API object

      // Send the message
      WhispirResponse response = sdk.sendMessage("61400000000",
          "This is the subject of my SMS",
          "This is the content of my SMS");

      // Status should be 202 Accepted
      System.out.println("Status: " + response.getStatusCode());


      // Retrieve a list of workspaces
      WhispirResponse workspaceResponse = sdk.getWorkspaces();

      TreeMap<String, String> workspaces = (TreeMap<String, String>) workspaceResponse

      // Iterate through the workspaces, printing the names and IDs out
      for (Map.Entry<String, String> entry : workspaces.entrySet()) {
        String workspaceName = entry.getKey();
        String workspaceId = entry.getValue();

        System.out.println(workspaceName + " => " + workspaceId);


      //Retrieve a list of scenarios

      WhispirResponse scenariosResponse = sdk.getScenarios();

      TreeMap<String, String> scenarios = (TreeMap<String, String>) scenariosResponse

      // Iterate through the workspaces, printing the names and IDs out
      for (Map.Entry<String, String> entry : scenarios.entrySet()) {
        String scenarioName = entry.getKey();
        String scenarioId = entry.getValue();

        System.out.println(scenarioName + " => " + scenarioId);

      //execute the scenario

      String scenarioId = "...";
      String workspaceId = "...";

      status = sdk.sendScenario(workspaceId, scenarioId);

      // Status should be 202 Accepted
      System.out.println("Status: " + status);

    } catch (WhispirSDKException e) {


This SDK is provided for use within your projects to simplify the use of Whispir's API.

The support of this code (and any potential bugs within) is not included under the SLA or contractual obligations within customers agreements with Whispir.

Whispir will provide a best effort to ensure this repository is bug free.

Please submit any issues via GitHub, or alternatively, fix the code and submit a pull request.

Terms and Conditions

See the LICENSE.txt and refer to Whispir's Terms of Service.

Change Log

Updates November 23, 2018 - Release 2.3.0

Added the following:

  • Updated the SDK to handle the API gateway changes. You would now be able to connect to the regional api gateways
  • Upgraded pom.xml; org.apache.httpcomponents:httpclient to now use version 4.3.6 or later to fix the vulnerability described in CVE-2015-5262

Updates April 22, 2016 - Release 2.2.2

Added the following:

  • Fixed a bug with DNS lookup when debugHost was being used to specify a non-production host. This is only relevant for customers doing testing in a sandbox environment.

Updates April 21, 2016 - Release 2.2.1

Added the following:

  • Added support for AuthCache when making connections through proxy. This was causing duplicate requests.
  • Refactored some of the tests to utlise workspaces.

Updates 29/06/2015

Released to Maven Central

Installation steps updated to reference Maven dependency instead of building from source.

Updates 26/06/2015 - Release 2.2.0

Added the following:

  • Added getSingleMessage and getSingleWorkspace functions
  • Refactored some of the tests to make them run when no Test Workspace has been defined

Updates 7/06/2015 - Release 2.1.0

Added the following:

  • Support for Basic Proxy Authentication (thanks to a pull request by vlsinitsyn)
  • Support for Creating Scenarios
  • Support for Creating Workspaces


  • I changed the default response type to WhispirResponse from int for POST requests. This was because I needed to get the header information for managing Scenarios and it's just a generally cleaner approach.

Bugs/Known Issues:

  • Currently, you can't create a Scenario in the default workspace, you need to specify a workspace ID. This is due to a bug in Whispir that will be fixed in an upcoming release.
  • After creating workspaces via the API, a login to Whispir is required. This rebuilds the cache and allows the workspace to be used. A subseqent release of Whispir will resolve this issue.
You can’t perform that action at this time.