Increase Java API Library

The Increase Java SDK provides convenient access to the Increase REST API from applications written in Java.

The Increase Java SDK is similar to the Increase Kotlin SDK but with minor differences that make it more ergonomic for use in Java, such as Optional instead of nullable values, Stream instead of Sequence, and CompletableFuture instead of suspend functions.

The REST API documentation can be found on increase.com. Javadocs are available on javadoc.io.

Installation

Gradle

implementation("com.increase.api:increase-java:0.570.0")

Maven

<dependency>
<groupId>com.increase.api</groupId>
<artifactId>increase-java</artifactId>
<version>0.570.0</version>
</dependency>

Requirements

This library requires Java 8 or later.

Usage

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
importcom.increase.api.models.accounts.Account;
importcom.increase.api.models.accounts.AccountCreateParams;
// Configures using the `increase.apiKey`, `increase.webhookSecret` and `increase.baseUrl` system properties// Or configures using the `INCREASE_API_KEY`, `INCREASE_WEBHOOK_SECRET` and `INCREASE_BASE_URL` environment variablesIncreaseClientclient = IncreaseOkHttpClient.fromEnv();
AccountCreateParamsparams = AccountCreateParams.builder()
.name("New Account!")
.entityId("entity_n8y8tnk2p9339ti393yi")
.programId("program_i2v2os4mwza1oetokh9i")
.build();
Accountaccount = client.accounts().create(params);

Client configuration

Configure the client using system properties or environment variables:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
// Configures using the `increase.apiKey`, `increase.webhookSecret` and `increase.baseUrl` system properties// Or configures using the `INCREASE_API_KEY`, `INCREASE_WEBHOOK_SECRET` and `INCREASE_BASE_URL` environment variablesIncreaseClientclient = IncreaseOkHttpClient.fromEnv();

Or manually:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
IncreaseClientclient = IncreaseOkHttpClient.builder()
.apiKey("My API Key")
.build();

Or using a combination of the two approaches:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
IncreaseClientclient = IncreaseOkHttpClient.builder()
// Configures using the `increase.apiKey`, `increase.webhookSecret` and `increase.baseUrl` system properties// Or configures using the `INCREASE_API_KEY`, `INCREASE_WEBHOOK_SECRET` and `INCREASE_BASE_URL` environment variables
.fromEnv()
.apiKey("My API Key")
.build();

See this table for the available options:

Setter	System property	Environment variable	Required	Default value
apiKey	increase.apiKey	INCREASE_API_KEY	true	-
webhookSecret	increase.webhookSecret	INCREASE_WEBHOOK_SECRET	false	-
baseUrl	increase.baseUrl	INCREASE_BASE_URL	true	"https://api.increase.com"

System properties take precedence over environment variables.

Tip

Don't create more than one client in the same application. Each client has a connection pool and thread pools, which are more efficient to share between requests.

Modifying configuration

To temporarily use a modified client configuration, while reusing the same connection and thread pools, call withOptions() on any client or service:

importcom.increase.api.client.IncreaseClient;
IncreaseClientclientWithOptions = client.withOptions(optionsBuilder -> {
optionsBuilder.baseUrl("https://example.com");
optionsBuilder.maxRetries(42);
});

The withOptions() method does not affect the original client or service.

Requests and responses

To send a request to the Increase API, build an instance of some Params class and pass it to the corresponding client method. When the response is received, it will be deserialized into an instance of a Java class.

For example, client.accounts().create(...) should be called with an instance of AccountCreateParams, and it will return an instance of Account.

Immutability

Each class in the SDK has an associated builder or factory method for constructing it.

Each class is immutable once constructed. If the class has an associated builder, then it has a toBuilder() method, which can be used to convert it back to a builder for making a modified copy.

Because each class is immutable, builder modification will never affect already built class instances.

Asynchronous execution

The default client is synchronous. To switch to asynchronous execution, call the async() method:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
importcom.increase.api.models.accounts.Account;
importcom.increase.api.models.accounts.AccountCreateParams;
importjava.util.concurrent.CompletableFuture;
// Configures using the `increase.apiKey`, `increase.webhookSecret` and `increase.baseUrl` system properties// Or configures using the `INCREASE_API_KEY`, `INCREASE_WEBHOOK_SECRET` and `INCREASE_BASE_URL` environment variablesIncreaseClientclient = IncreaseOkHttpClient.fromEnv();
AccountCreateParamsparams = AccountCreateParams.builder()
.name("New Account!")
.entityId("entity_n8y8tnk2p9339ti393yi")
.programId("program_i2v2os4mwza1oetokh9i")
.build();
CompletableFuture<Account> account = client.async().accounts().create(params);

Or create an asynchronous client from the beginning:

importcom.increase.api.client.IncreaseClientAsync;
importcom.increase.api.client.okhttp.IncreaseOkHttpClientAsync;
importcom.increase.api.models.accounts.Account;
importcom.increase.api.models.accounts.AccountCreateParams;
importjava.util.concurrent.CompletableFuture;
// Configures using the `increase.apiKey`, `increase.webhookSecret` and `increase.baseUrl` system properties// Or configures using the `INCREASE_API_KEY`, `INCREASE_WEBHOOK_SECRET` and `INCREASE_BASE_URL` environment variablesIncreaseClientAsyncclient = IncreaseOkHttpClientAsync.fromEnv();
AccountCreateParamsparams = AccountCreateParams.builder()
.name("New Account!")
.entityId("entity_n8y8tnk2p9339ti393yi")
.programId("program_i2v2os4mwza1oetokh9i")
.build();
CompletableFuture<Account> account = client.accounts().create(params);

The asynchronous client supports the same options as the synchronous one, except most methods return CompletableFutures.

File uploads

The SDK defines methods that accept files.

To upload a file, pass a Path:

importcom.increase.api.models.files.File;
importcom.increase.api.models.files.FileCreateParams;
importjava.nio.file.Paths;
FileCreateParamsparams = FileCreateParams.builder()
.purpose(FileCreateParams.Purpose.CHECK_IMAGE_FRONT)
.file(Paths.get("my/file.txt"))
.build();
Filefile = client.files().create(params);

Or an arbitrary InputStream:

importcom.increase.api.models.files.File;
importcom.increase.api.models.files.FileCreateParams;
importjava.net.URL;
FileCreateParamsparams = FileCreateParams.builder()
.purpose(FileCreateParams.Purpose.CHECK_IMAGE_FRONT)
.file(newURL("https://example.com/my/file.txt").openStream())
.build();
Filefile = client.files().create(params);

Or a byte[] array:

importcom.increase.api.models.files.File;
importcom.increase.api.models.files.FileCreateParams;
FileCreateParamsparams = FileCreateParams.builder()
.purpose(FileCreateParams.Purpose.CHECK_IMAGE_FRONT)
.file("content".getBytes())
.build();
Filefile = client.files().create(params);

Note that when passing a non-Path its filename is unknown so it will not be included in the request. To manually set a filename, pass a MultipartField:

importcom.increase.api.core.MultipartField;
importcom.increase.api.models.files.File;
importcom.increase.api.models.files.FileCreateParams;
importjava.io.InputStream;
importjava.net.URL;
FileCreateParamsparams = FileCreateParams.builder()
.purpose(FileCreateParams.Purpose.CHECK_IMAGE_FRONT)
.file(MultipartField.<InputStream>builder()
.value(newURL("https://example.com/my/file.txt").openStream())
.filename("my/file.txt")
.build())
.build();
Filefile = client.files().create(params);

Binary responses

The SDK defines methods that return binary responses, which are used for API responses that shouldn't necessarily be parsed, like non-JSON data.

These methods return HttpResponse:

importcom.increase.api.core.http.HttpResponse;
importcom.increase.api.models.files.FileContentsParams;
HttpResponseresponse = client.files().contents("file_makxrc67oh9l6sg7w9yc");

To save the response content to a file, use the Files.copy(...) method:

importcom.increase.api.core.http.HttpResponse;
importjava.nio.file.Files;
importjava.nio.file.Paths;
importjava.nio.file.StandardCopyOption;
try (HttpResponseresponse = client.files().contents(params)) {
Files.copy(
response.body(),
Paths.get(path),
StandardCopyOption.REPLACE_EXISTING
);
} catch (Exceptione) {
System.out.println("Something went wrong!");
thrownewRuntimeException(e);
}

Or transfer the response content to any OutputStream:

importcom.increase.api.core.http.HttpResponse;
importjava.nio.file.Files;
importjava.nio.file.Paths;
try (HttpResponseresponse = client.files().contents(params)) {
response.body().transferTo(Files.newOutputStream(Paths.get(path)));
} catch (Exceptione) {
System.out.println("Something went wrong!");
thrownewRuntimeException(e);
}

Raw responses

The SDK defines methods that deserialize responses into instances of Java classes. However, these methods don't provide access to the response headers, status code, or the raw response body.

To access this data, prefix any HTTP method call on a client or service with withRawResponse():

importcom.increase.api.core.http.Headers;
importcom.increase.api.core.http.HttpResponseFor;
importcom.increase.api.models.accounts.Account;
importcom.increase.api.models.accounts.AccountCreateParams;
AccountCreateParamsparams = AccountCreateParams.builder()
.name("New Account!")
.entityId("entity_n8y8tnk2p9339ti393yi")
.programId("program_i2v2os4mwza1oetokh9i")
.build();
HttpResponseFor<Account> account = client.accounts().withRawResponse().create(params);
intstatusCode = account.statusCode();
Headersheaders = account.headers();

You can still deserialize the response into an instance of a Java class if needed:

importcom.increase.api.models.accounts.Account;
AccountparsedAccount = account.parse();

Error handling

The SDK throws custom unchecked exception types:

• IncreaseServiceException: Base class for HTTP errors. See this table for which exception subclass is thrown for each HTTP status code:

  Status	Exception
  400	BadRequestException
  401	UnauthorizedException
  403	PermissionDeniedException
  404	NotFoundException
  422	UnprocessableEntityException
  429	RateLimitException
  5xx	InternalServerException
  others	UnexpectedStatusCodeException

• IncreaseIoException: I/O networking errors.

• IncreaseRetryableException: Generic error indicating a failure that could be retried by the client.

• IncreaseInvalidDataException: Failure to interpret successfully parsed data. For example, when accessing a property that's supposed to be required, but the API unexpectedly omitted it from the response.

• IncreaseException: Base class for all exceptions. Most errors will result in one of the previously mentioned ones, but completely generic errors may be thrown using the base class.

Pagination

The SDK defines methods that return a paginated lists of results. It provides convenient ways to access the results either one page at a time or item-by-item across all pages.

Auto-pagination

To iterate through all results across all pages, use the autoPager() method, which automatically fetches more pages as needed.

When using the synchronous client, the method returns an Iterable

importcom.increase.api.models.accounts.Account;
importcom.increase.api.models.accounts.AccountListPage;
AccountListPagepage = client.accounts().list();
// Process as an Iterablefor (Accountaccount : page.autoPager()) {
System.out.println(account);
}
// Process as a Streampage.autoPager()
.stream()
.limit(50)
.forEach(account -> System.out.println(account));

When using the asynchronous client, the method returns an AsyncStreamResponse:

importcom.increase.api.core.http.AsyncStreamResponse;
importcom.increase.api.models.accounts.Account;
importcom.increase.api.models.accounts.AccountListPageAsync;
importjava.util.Optional;
importjava.util.concurrent.CompletableFuture;
CompletableFuture<AccountListPageAsync> pageFuture = client.async().accounts().list();
pageFuture.thenRun(page -> page.autoPager().subscribe(account -> {
System.out.println(account);
}));
// If you need to handle errors or completion of the streampageFuture.thenRun(page -> page.autoPager().subscribe(newAsyncStreamResponse.Handler<>() {
@OverridepublicvoidonNext(Accountaccount) {
System.out.println(account);
}
@OverridepublicvoidonComplete(Optional<Throwable> error) {
if (error.isPresent()) {
System.out.println("Something went wrong!");
thrownewRuntimeException(error.get());
} else {
System.out.println("No more!");
}
}
}));
// Or use futurespageFuture.thenRun(page -> page.autoPager()
.subscribe(account -> {
System.out.println(account);
})
.onCompleteFuture()
.whenComplete((unused, error) -> {
if (error != null) {
System.out.println("Something went wrong!");
thrownewRuntimeException(error);
} else {
System.out.println("No more!");
}
}));

Manual pagination

To access individual page items and manually request the next page, use the items(), hasNextPage(), and nextPage() methods:

importcom.increase.api.models.accounts.Account;
importcom.increase.api.models.accounts.AccountListPage;
AccountListPagepage = client.accounts().list();
while (true) {
for (Accountaccount : page.items()) {
System.out.println(account);
}
if (!page.hasNextPage()) {
break;
}
page = page.nextPage();
}

Logging

Enable logging by setting the INCREASE_LOG environment variable to info:

export INCREASE_LOG=info

Or to debug for more verbose logging:

export INCREASE_LOG=debug

Or configure the client manually using the logLevel method:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
importcom.increase.api.core.LogLevel;
IncreaseClientclient = IncreaseOkHttpClient.builder()
.fromEnv()
.logLevel(LogLevel.INFO)
.build();

Webhook Verification

We provide helper methods for verifying that a webhook request came from Increase, and not a malicious third party.

You can use increase.events().unwrap(UnwrapWebhookParams) to both verify the signature and parse the event body into a typed UnwrapWebhookEvent. An IncreaseWebhookException will be thrown if the signature is invalid.

Note that the body parameter must be the raw JSON string sent from the server (do not parse it first). If headers is omitted, the body will be unwrapped without any signature validation.

ProGuard and R8

Although the SDK uses reflection, it is still usable with ProGuard and R8 because increase-java-core is published with a configuration file containing keep rules.

ProGuard and R8 should automatically detect and use the published rules, but you can also manually copy the keep rules if necessary.

Jackson

The SDK depends on Jackson for JSON serialization/deserialization. It is compatible with version 2.13.4 or higher, but depends on version 2.18.2 by default.

The SDK throws an exception if it detects an incompatible Jackson version at runtime (e.g. if the default version was overridden in your Maven or Gradle config).

If the SDK threw an exception, but you're certain the version is compatible, then disable the version check using the checkJacksonVersionCompatibility on IncreaseOkHttpClient or IncreaseOkHttpClientAsync.

Caution

We make no guarantee that the SDK works correctly when the Jackson version check is disabled.

Also note that there are bugs in older Jackson versions that can affect the SDK. We don't work around all Jackson bugs (example) and expect users to upgrade Jackson for those instead.

Network options

Retries

The SDK automatically retries 2 times by default, with a short exponential backoff between requests.

Only the following error types are retried:

• Connection errors (for example, due to a network connectivity problem)
• 408 Request Timeout
• 409 Conflict
• 429 Rate Limit
• 5xx Internal

The API may also explicitly instruct the SDK to retry or not retry a request.

To set a custom number of retries, configure the client using the maxRetries method:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
IncreaseClientclient = IncreaseOkHttpClient.builder()
.fromEnv()
.maxRetries(4)
.build();

Timeouts

Requests time out after 1 minute by default.

To set a custom timeout, configure the method call using the timeout method:

importcom.increase.api.models.accounts.Account;
Accountaccount = client.accounts().create(
params, RequestOptions.builder().timeout(Duration.ofSeconds(30)).build()
);

Or configure the default for all method calls at the client level:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
importjava.time.Duration;
IncreaseClientclient = IncreaseOkHttpClient.builder()
.fromEnv()
.timeout(Duration.ofSeconds(30))
.build();

Proxies

To route requests through a proxy, configure the client using the proxy method:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
importjava.net.InetSocketAddress;
importjava.net.Proxy;
IncreaseClientclient = IncreaseOkHttpClient.builder()
.fromEnv()
.proxy(newProxy(
Proxy.Type.HTTP, newInetSocketAddress(
"https://example.com", 8080
)
))
.build();

If the proxy responds with 407 Proxy Authentication Required, supply credentials by also configuring proxyAuthenticator:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
importcom.increase.api.core.http.ProxyAuthenticator;
IncreaseClientclient = IncreaseOkHttpClient.builder()
.fromEnv()
.proxy(...)
// Or a custom implementation of `ProxyAuthenticator`.
.proxyAuthenticator(ProxyAuthenticator.basic("username", "password"))
.build();

Connection pooling

To customize the underlying OkHttp connection pool, configure the client using the maxIdleConnections and keepAliveDuration methods:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
importjava.time.Duration;
IncreaseClientclient = IncreaseOkHttpClient.builder()
.fromEnv()
// If `maxIdleConnections` is set, then `keepAliveDuration` must be set, and vice versa.
.maxIdleConnections(10)
.keepAliveDuration(Duration.ofMinutes(2))
.build();

If both options are unset, OkHttp's default connection pool settings are used.

HTTPS

Note

Most applications should not call these methods, and instead use the system defaults. The defaults include special optimizations that can be lost if the implementations are modified.

To configure how HTTPS connections are secured, configure the client using the sslSocketFactory, trustManager, and hostnameVerifier methods:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
IncreaseClientclient = IncreaseOkHttpClient.builder()
.fromEnv()
// If `sslSocketFactory` is set, then `trustManager` must be set, and vice versa.
.sslSocketFactory(yourSSLSocketFactory)
.trustManager(yourTrustManager)
.hostnameVerifier(yourHostnameVerifier)
.build();

Environments

The SDK sends requests to the production by default. To send requests to a different environment, configure the client like so:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
IncreaseClientclient = IncreaseOkHttpClient.builder()
.fromEnv()
.sandbox()
.build();

Custom HTTP client

The SDK consists of three artifacts:

• increase-java-core
  • Contains core SDK logic
  • Does not depend on OkHttp
  • Exposes IncreaseClient, IncreaseClientAsync, IncreaseClientImpl, and IncreaseClientAsyncImpl, all of which can work with any HTTP client
• increase-java-client-okhttp
  • Depends on OkHttp
  • Exposes IncreaseOkHttpClient and IncreaseOkHttpClientAsync, which provide a way to construct IncreaseClientImpl and IncreaseClientAsyncImpl, respectively, using OkHttp
• increase-java
  • Depends on and exposes the APIs of both increase-java-core and increase-java-client-okhttp
  • Does not have its own logic

This structure allows replacing the SDK's default HTTP client without pulling in unnecessary dependencies.

Customized OkHttpClient

Tip

Try the available network options before replacing the default client.

To use a customized OkHttpClient:

1. Replace your increase-java dependency with increase-java-core
2. Copy increase-java-client-okhttp's OkHttpClient class into your code and customize it
3. Construct IncreaseClientImpl or IncreaseClientAsyncImpl, similarly to IncreaseOkHttpClient or IncreaseOkHttpClientAsync, using your customized client

Completely custom HTTP client

To use a completely custom HTTP client:

1. Replace your increase-java dependency with increase-java-core
2. Write a class that implements the HttpClient interface
3. Construct IncreaseClientImpl or IncreaseClientAsyncImpl, similarly to IncreaseOkHttpClient or IncreaseOkHttpClientAsync, using your new client class

Undocumented API functionality

The SDK is typed for convenient usage of the documented API. However, it also supports working with undocumented or not yet supported parts of the API.

Parameters

To set undocumented parameters, call the putAdditionalHeader, putAdditionalQueryParam, or putAdditionalBodyProperty methods on any Params class:

importcom.increase.api.core.JsonValue;
importcom.increase.api.models.accounts.AccountCreateParams;
AccountCreateParamsparams = AccountCreateParams.builder()
.putAdditionalHeader("Secret-Header", "42")
.putAdditionalQueryParam("secret_query_param", "42")
.putAdditionalBodyProperty("secretProperty", JsonValue.from("42"))
.build();

These can be accessed on the built object later using the _additionalHeaders(), _additionalQueryParams(), and _additionalBodyProperties() methods.

To set a documented parameter or property to an undocumented or not yet supported value, pass a JsonValue object to its setter:

importcom.increase.api.core.JsonValue;
importcom.increase.api.models.accounts.AccountCreateParams;
AccountCreateParamsparams = AccountCreateParams.builder()
.name(JsonValue.from(42))
.entityId("entity_n8y8tnk2p9339ti393yi")
.programId("program_i2v2os4mwza1oetokh9i")
.build();

The most straightforward way to create a JsonValue is using its from(...) method:

importcom.increase.api.core.JsonValue;
importjava.util.List;
importjava.util.Map;
// Create primitive JSON valuesJsonValuenullValue = JsonValue.from(null);
JsonValuebooleanValue = JsonValue.from(true);
JsonValuenumberValue = JsonValue.from(42);
JsonValuestringValue = JsonValue.from("Hello World!");
// Create a JSON array value equivalent to `["Hello", "World"]`JsonValuearrayValue = JsonValue.from(List.of(
"Hello", "World"
));
// Create a JSON object value equivalent to `{ "a": 1, "b": 2 }`JsonValueobjectValue = JsonValue.from(Map.of(
"a", 1,
"b", 2
));
// Create an arbitrarily nested JSON equivalent to:// {// "a": [1, 2],// "b": [3, 4]// }JsonValuecomplexValue = JsonValue.from(Map.of(
"a", List.of(
1, 2
),
"b", List.of(
3, 4
)
));

Normally a Builder class's build method will throw IllegalStateException if any required parameter or property is unset.

To forcibly omit a required parameter or property, pass JsonMissing:

importcom.increase.api.core.JsonMissing;
importcom.increase.api.models.accounts.AccountCreateParams;
AccountCreateParamsparams = AccountCreateParams.builder()
.name(JsonMissing.of())
.build();

Response properties

To access undocumented response properties, call the _additionalProperties() method:

importcom.increase.api.core.JsonValue;
importjava.util.Map;
Map<String, JsonValue> additionalProperties = client.accounts().create(params)._additionalProperties();
JsonValuesecretPropertyValue = additionalProperties.get("secretProperty");
Stringresult = secretPropertyValue.accept(newJsonValue.Visitor<>() {
@OverridepublicStringvisitNull() {
return"It's null!";
}
@OverridepublicStringvisitBoolean(booleanvalue) {
return"It's a boolean!";
}
@OverridepublicStringvisitNumber(Numbervalue) {
return"It's a number!";
}
// Other methods include `visitMissing`, `visitString`, `visitArray`, and `visitObject`// The default implementation of each unimplemented method delegates to `visitDefault`, which throws by default, but can also be overridden
});

To access a property's raw JSON value, which may be undocumented, call its _ prefixed method:

importcom.increase.api.core.JsonField;
importjava.util.Optional;
JsonField<String> name = client.accounts().create(params)._name();
if (name.isMissing()) {
// The property is absent from the JSON response
} elseif (name.isNull()) {
// The property was set to literal null
} else {
// Check if value was provided as a string// Other methods include `asNumber()`, `asBoolean()`, etc.Optional<String> jsonString = name.asString();
// Try to deserialize into a custom typeMyClassmyObject = name.asUnknown().orElseThrow().convert(MyClass.class);
}

Response validation

In rare cases, the API may return a response that doesn't match the expected type. For example, the SDK may expect a property to contain a String, but the API could return something else.

By default, the SDK will not throw an exception in this case. It will throw IncreaseInvalidDataException only if you directly access the property.

Validating the response is not forwards compatible with new types from the API for existing fields.

If you would still prefer to check that the response is completely well-typed upfront, then either call validate():

importcom.increase.api.models.accounts.Account;
Accountaccount = client.accounts().create(params).validate();

Or configure the method call to validate the response using the responseValidation method:

importcom.increase.api.models.accounts.Account;
Accountaccount = client.accounts().create(
params, RequestOptions.builder().responseValidation(true).build()
);

Or configure the default for all method calls at the client level:

importcom.increase.api.client.IncreaseClient;
importcom.increase.api.client.okhttp.IncreaseOkHttpClient;
IncreaseClientclient = IncreaseOkHttpClient.builder()
.fromEnv()
.responseValidation(true)
.build();

FAQ

Why don't you use plain enum classes?

Java enum classes are not trivially forwards compatible. Using them in the SDK could cause runtime exceptions if the API is updated to respond with a new enum value.

Why do you represent fields using JsonField<T> instead of just plain T?

Using JsonField<T> enables a few features:

• Allowing usage of undocumented API functionality
• Lazily validating the API response against the expected shape
• Representing absent vs explicitly null values

Why don't you use data classes?

It is not backwards compatible to add new fields to a data class and we don't want to introduce a breaking change every time we add a field to a class.

Why don't you use checked exceptions?

Checked exceptions are widely considered a mistake in the Java programming language. In fact, they were omitted from Kotlin for this reason.

Checked exceptions:

• Are verbose to handle
• Encourage error handling at the wrong level of abstraction, where nothing can be done about the error
• Are tedious to propagate due to the function coloring problem
• Don't play well with lambdas (also due to the function coloring problem)

Semantic versioning

This package generally follows SemVer conventions, though certain backwards-incompatible changes may be released as minor versions:

1. Changes to library internals which are technically public but not intended or documented for external use. (Please open a GitHub issue to let us know if you are relying on such internals.)
2. Changes that we do not expect to impact the vast majority of users in practice.

We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.

We are keen for your feedback; please open an issue with questions, bugs, or suggestions.