The documentation for the Twilio API can be found here.
The Java library documentation can be found here.
twilio-java
uses a modified version of Semantic Versioning for all changes. See this document for details.
New accounts and subaccounts are now required to use TLS 1.2 when accessing the REST API. "Upgrade Required" errors indicate that TLS 1.0/1.1 is being used.
This library supports the following Java implementations:
For Java 7 support, use twilio-java
major version 7.X.X
.
To indicate that a class or method is in beta and subject to change, we use the @Beta
annotation. For example:
@Beta
public class ClassName {
// Class implementation
}
public class ClassName {
@Beta
public void init() {
// Implementation
}
}
twilio-java
uses Maven. At present the jars are available from a public maven repository.
Use the following dependency in your project to grab via Maven:
<dependency>
<groupId>com.twilio.sdk</groupId>
<artifactId>twilio</artifactId>
<version>10.X.X</version>
<scope>compile</scope>
</dependency>
or Gradle:
implementation "com.twilio.sdk:twilio:10.X.X"
If you want to compile it yourself, here's how:
git clone git@github.com:twilio/twilio-java
cd twilio-java
mvn install # Requires maven, download from https://maven.apache.org/download.html
If you want to build your own .jar, execute the following from within the cloned directory:
mvn package
If you run into trouble with local tests, use:
mvn package -Dmaven.test.skip=true
Try sending yourself an SMS message, like this:
import com.twilio.Twilio;
import com.twilio.rest.api.v2010.account.Message;
import com.twilio.type.PhoneNumber;
public class Example {
// Find your Account Sid and Token at console.twilio.com
public static final String ACCOUNT_SID = "ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
public static final String AUTH_TOKEN = "your_auth_token";
public static void main(String[] args) {
Twilio.init(ACCOUNT_SID, AUTH_TOKEN);
Message message = Message
.creator(
new PhoneNumber("+15558675309"),
new PhoneNumber("+15017250604"),
"This is the ship that made the Kessel Run in fourteen parsecs?"
)
.create();
System.out.println(message.getSid());
}
}
Warning It's okay to hardcode your credentials when testing locally, but you should use environment variables to keep them secret before committing any code or deploying to production. Check out How to Set Environment Variables for more information.
import com.twilio.Twilio;
import com.twilio.exception.AuthenticationException;
public class Example {
private static final String ACCOUNT_SID =
"ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
private static final String AUTH_TOKEN = "your_auth_token";
public static void main(String[] args) throws AuthenticationException {
Twilio.init(ACCOUNT_SID, AUTH_TOKEN);
}
}
The above example shows how to initialize the client in case the endpoints use basic authentication. When the endpoint does not require any authentication, use TwilioNoAuth client instead. There are endpoints like Organization domain which uses bearer token authentication. Custom Clients needs to be used in such cases and initialize them with the values required for access token generation.
To bypass the initialization step you can also use a custom token manager implementation. Token manager class should implement the Token interface and call a token generation endpoint of your choice. Detailed examples here
twilio-java
supports the credentials, region, and edge values stored in the following environment variables:
TWILIO_ACCOUNT_SID
TWILIO_AUTH_TOKEN
TWILIO_REGION
TWILIO_EDGE
If using these variables, the above client initialization can be skipped.
import com.twilio.Twilio;
import com.twilio.rest.api.v2010.account.Call;
import com.twilio.type.PhoneNumber;
import java.net.URI;
import java.net.URISyntaxException;
public class Example {
public static final String ACCOUNT_SID = "ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
public static final String AUTH_TOKEN = "your_auth_token";
public static void main(String[] args) throws URISyntaxException {
Twilio.init(ACCOUNT_SID, AUTH_TOKEN);
Call call = Call
.creator(
new PhoneNumber("+14155551212"),
new PhoneNumber("+15017250604"),
new URI("http://demo.twilio.com/docs/voice.xml")
)
.create();
System.out.println(call.getSid());
}
}
import com.twilio.Twilio;
import com.twilio.rest.api.v2010.account.Call;
public class Example {
public static final String ACCOUNT_SID = "ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
public static final String AUTH_TOKEN = "your_auth_token";
public static void main(String[] args) {
Twilio.init(ACCOUNT_SID, AUTH_TOKEN);
Call call = Call.fetcher("CA42ed11f93dc08b952027ffbc406d0868").fetch();
System.out.println(call.getTo());
}
}
We are introducing Client Credentials Flow-based OAuth 2.0 authentication.
This feature is currently in beta
and its implementation is subject to change.
The library automatically handles paging for you. With the read
method, you can specify the number of records you want to receive (limit
) and the maximum size you want each page fetch to be (pageSize
). The library will then handle the task for you, fetching new pages under the hood as you iterate over the records.
For more information, view the auto-generated library docs.
read
methodimport com.twilio.Twilio;
import com.twilio.base.ResourceSet;
import com.twilio.rest.api.v2010.account.Call;
public class Example {
public static final String ACCOUNT_SID = "ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
public static final String AUTH_TOKEN = "your_auth_token";
public static void main(String[] args) {
Twilio.init(ACCOUNT_SID, AUTH_TOKEN);
ResourceSet<Call> calls = Call.reader().read();
for (Call call : calls) {
System.out.println(call.getDirection());
}
}
}
To take advantage of Twilio's Global Infrastructure, specify the target Region and/or Edge for the client:
Twilio.init(accountSid, authToken);
Twilio.setRegion("au1");
Twilio.setEdge("sydney");
This will result in the hostname
transforming from api.twilio.com
to api.sydney.au1.twilio.com
.
This library uses SLF4J for logging. Consult the SFL4J documentation for information about logging configuration.
For example, if you are using log4j
:
log4j-slf4j-impl
, log4j-core
and log4j-api
in your pom.xml
fileDefine the logging level for the Twilio HTTP client in your configuration. For example, in src/main/resources/log4j2.xml
:
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN">
<Appenders>
<Console name="Console" target="SYSTEM_OUT">
<PatternLayout pattern="%d{HH:mm:ss.SSS} %-5level - %msg%n"/>
</Console>
</Appenders>
<Loggers>
<!--Your Twilio logging configuration goes here-->
<Logger name="com.twilio.http" level="debug" additivity="false">
<AppenderRef ref="Console"/>
</Logger>
<Root level="info">
<AppenderRef ref="Console"/>
</Root>
</Loggers>
</Configuration>
import com.twilio.exception.ApiException;
try {
Message message = Message.creator(
new PhoneNumber("+15558881234"), // To number
new PhoneNumber("+15559994321"), // From number
"Hello world!" // SMS body
).create();
System.out.println(message.getSid());
} catch (final ApiException e) {
System.err.println(e);
}
Additional documentation here: https://twilio.com/docs/iam/pkcv/quickstart
ValidationClient httpClient = new ValidationClient(ACCOUNT_SID, key.getSid(), signingKey.getSid(), pair.getPrivate());
TwilioRestClient client = new TwilioRestClient.Builder(signingKey.getSid(), signingKey.getSecret())
.accountSid(ACCOUNT_SID)
.httpClient(httpClient)
.build();
To control phone calls, your application needs to output TwiML.
TwiML in twilio-java now use the builder pattern!
TwiML twiml = new VoiceResponse.Builder()
.say(new Say.Builder("Hello World!").build())
.play(new Play.Builder("https://api.twilio.com/cowbell.mp3").loop(5).build())
.build();
That will output XML that looks like this:
<Response>
<Say>Hello World!</Say>
<Play loop="5">https://api.twilio.com/cowbell.mp3</Play>
</Response>
To use a custom HTTP client with this helper library, please see the advanced example of how to do so.
The Dockerfile
present in this repository and its respective twilio/twilio-java
Docker image are currently used by Twilio for testing purposes only.
If you need help installing or using the library, please check the Twilio Support Help Center first, and file a support ticket if you don't find an answer to your question.
If you've instead found a bug in the library or would like new features added, go ahead and open issues or pull requests against this repo!