NexmoClient class, which is probably what
you want.See: Description
| Interface | Description |
|---|---|
| Method<RequestT,ResultT> |
| Class | Description |
|---|---|
| AbstractClient |
Abstract class for different API clients.
|
| AbstractMethod<RequestT,ResultT> |
Abstract class to assist in implementing a call against a REST endpoint.
|
| HttpConfig | |
| HttpConfig.Builder | |
| HttpWrapper |
Internal class that holds available authentication methods and a shared HttpClient.
|
| NexmoClient |
Top-level Nexmo API client object.
|
| NexmoClient.Builder |
| Exception | Description |
|---|---|
| NexmoBadRequestException | |
| NexmoClientCreationException |
Indicates that there was a failure during NexmoClient creation.
|
| NexmoClientException | |
| NexmoMethodFailedException | |
| NexmoResponseParseException |
An exception that indicates the contents of an HttpResponse could not be parsed.
|
| NexmoUnableToReadPrivateKeyException | |
| NexmoUnexpectedException |
NexmoUnexpectedException indicates an exception that should not happen in an ideal world.
|
NexmoClient class, which is probably what
you want.
All behaviour is accessible via the NexmoClient class, which should be instantiated with one
or more AuthMethod objects from the com.nexmo.client.auth package.