Sinch Java SDK for Numbers

The Sinch Numbers Java SDK allows you to quickly interact with the Numbers API from inside your Java applications. The fastest way to get started with the SDK is to check out our getting started guides. There you'll find all the instructions necessary to download, install, set up, and start using the SDK.

Syntax

When using the Java SDK, the code representing requests and queries sent to and responses received from the Numbers API are structured similarly to those that are sent and received using the Numbers API itself.

The code sample on the side of this page is an example of how to use the Java SDK to list the available numbers of a given type and region. The code is also displayed below, along with a Numbers API call that accomplishes the same task, for reference:

import java.net.*;
import java.net.http.*;
import java.util.*;

public class App {
  public static void main(String[] args) throws Exception {
    var httpClient = HttpClient.newBuilder().build();

    var host = "https://numbers.api.sinch.com";
    var projectId = "YOUR_projectId";
    var pathname = "/v1/projects/" + projectId + "/availableNumbers";
    var request = HttpRequest.newBuilder()
      .GET()
      .uri(URI.create(host + pathname ))
      .header("Authorization", "Basic " + Base64.getEncoder().encodeToString(("YOUR_username:YOUR_password").getBytes()))
      .build();

    var response = httpClient.send(request, HttpResponse.BodyHandlers.ofString());

    System.out.println(response.body());
  }
}

package numbers;

import com.sinch.sdk.domains.numbers.api.v1.AvailableNumberService;
import com.sinch.sdk.domains.numbers.api.v1.NumbersService;
import com.sinch.sdk.domains.numbers.models.v1.NumberType;
import com.sinch.sdk.domains.numbers.models.v1.available.request.AvailableNumberListRequest;
import com.sinch.sdk.domains.numbers.models.v1.available.response.AvailableNumberListResponse;
import java.util.logging.Logger;

public class Snippet {

  private static final Logger LOGGER = Logger.getLogger(Snippet.class.getName());

  static void execute(NumbersService numbersService) {

    AvailableNumberService availableNumbersService = numbersService.available();

    String regionCode = "US";
    NumberType type = NumberType.LOCAL;

    AvailableNumberListRequest parameters =
        AvailableNumberListRequest.builder()
            .setRegionCode(regionCode)
            .setType(type)
            .build();

    AvailableNumberListResponse response = availableNumbersService.list(parameters);

    response
        .iterator()
        .forEachRemaining(
            number -> LOGGER.info(String.format("Available number details: %s", number)));
  }
}

Client

When using the Sinch Java SDK, you initialize communication with the Sinch backend by initializing the Java SDK's main client class. This client allows you to access the functionality of the Sinch Java SDK.

Initialization

To successfully initialize the Sinch client class, you must provide a valid access key ID and access key secret combination. You must also provide your Project ID. For example:

package numbers.sdk;

import com.sinch.sdk.SinchClient;

public class App {
    
    public static String access_key = "YOUR_access_key";
    public static String access_secret = "YOUR_access_secret";
    public static String project_id = "YOUR_project_id"

    public static void main(String[] args) {
        
      SinchClient client = new SinchClient(Configuration.builder()
                                  .setKeyId(access_key)
                                  .setKeySecret(access_secret)
                                  .setProjectId(project_id)
                                  .build());
}

Numbers domain

Endpoint categories

In the Sinch Java SDK, Numbers API endpoints are accessible through the client:

• numbers().v1()
• numbers().v1().regions()
• numbers().v1().callbackConfiguration()
• numbers().v1().webhooks()

For example:

var numbers = client.numbers().v1().list(AvailableNumberListRequest.builder()
                                                                .setType(NumberType.LOCAL)
                                                                .setRegionCode("US")
                                                                .build());

The field mappings are described in the sections below.

numbers().v1() endpoint category

numbers().v1().regions() endpoint category

numbers().v1().callbackConfiguration() endpoint category

numbers().v1().webhooks() endpoint category

Request and query parameters

Requests and queries made using the Java SDK are similar to those made using the SMS API. Many of the fields are named and structured similarly. For example, consider the representations of an SMS API message type. One field is represented in JSON, and the other is using our Java SDK:

NumberType.MOBILE

"type": "MOBILE"

Many fields in the Java SDK are rendered as enums in data models.

Nested objects

When making calls directly to the API, we use JSON objects, including (in some cases) nested JSON objects. When using the Java SDK, we use Java data models instead of nested JSON objects. For example, consider the SMS configuration objects below. One is represented in JSON, the other as a Java object:

AvailableNumberListRequest.builder()
                        .setType(NumberType.LOCAL)
                        .setRegionCode("US")
                        .build()

{
  "type": "LOCAL",
  "regionCode": "US"
}

Responses

Response fields match the API responses. They are delivered as Java objects.