Lithic Kotlin API Library

The Lithic Kotlin SDK provides convenient access to the Lithic REST API from applications written in Kotlin.

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

The REST API documentation can be found on docs.lithic.com.

Installation

Gradle

implementation("com.lithic.api:lithic-kotlin:0.78.0")

Maven

<dependency>
    <groupId>com.lithic.api</groupId>
    <artifactId>lithic-kotlin</artifactId>
    <version>0.78.0</version>
</dependency>

Requirements

This library requires Java 8 or later.

Usage

import com.lithic.api.client.LithicClient
import com.lithic.api.client.okhttp.LithicOkHttpClient
import com.lithic.api.models.Card
import com.lithic.api.models.CardCreateParams

// Configures using the `LITHIC_API_KEY` and `LITHIC_WEBHOOK_SECRET` environment variables
val client: LithicClient = LithicOkHttpClient.fromEnv()

val params: CardCreateParams = CardCreateParams.builder()
    .type(CardCreateParams.Type.SINGLE_USE)
    .build()
val card: Card = client.cards().create(params)

Client configuration

Configure the client using environment variables:

import com.lithic.api.client.LithicClient
import com.lithic.api.client.okhttp.LithicOkHttpClient

// Configures using the `LITHIC_API_KEY` and `LITHIC_WEBHOOK_SECRET` environment variables
val client: LithicClient = LithicOkHttpClient.fromEnv()

Or manually:

import com.lithic.api.client.LithicClient
import com.lithic.api.client.okhttp.LithicOkHttpClient

val client: LithicClient = LithicOkHttpClient.builder()
    .apiKey("My Lithic API Key")
    .build()

Or using a combination of the two approaches:

import com.lithic.api.client.LithicClient
import com.lithic.api.client.okhttp.LithicOkHttpClient

val client: LithicClient = LithicOkHttpClient.builder()
    // Configures using the `LITHIC_API_KEY` and `LITHIC_WEBHOOK_SECRET` environment variables
    .fromEnv()
    .apiKey("My Lithic API Key")
    .build()

See this table for the available options:

Setter	Environment variable	Required	Default value
apiKey	LITHIC_API_KEY	true	-
webhookSecret	LITHIC_WEBHOOK_SECRET	false	-

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.

Requests and responses

To send a request to the Lithic 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 Kotlin class.

For example, client.cards().create(...) should be called with an instance of CardCreateParams, and it will return an instance of Card.

Asynchronous execution

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

import com.lithic.api.client.LithicClient
import com.lithic.api.client.okhttp.LithicOkHttpClient
import com.lithic.api.models.Card
import com.lithic.api.models.CardCreateParams

// Configures using the `LITHIC_API_KEY` and `LITHIC_WEBHOOK_SECRET` environment variables
val client: LithicClient = LithicOkHttpClient.fromEnv()

val params: CardCreateParams = CardCreateParams.builder()
    .type(CardCreateParams.Type.SINGLE_USE)
    .build()
val card: Card = client.async().cards().create(params)

Or create an asynchronous client from the beginning:

import com.lithic.api.client.LithicClientAsync
import com.lithic.api.client.okhttp.LithicOkHttpClientAsync
import com.lithic.api.models.Card
import com.lithic.api.models.CardCreateParams

// Configures using the `LITHIC_API_KEY` and `LITHIC_WEBHOOK_SECRET` environment variables
val client: LithicClientAsync = LithicOkHttpClientAsync.fromEnv()

val params: CardCreateParams = CardCreateParams.builder()
    .type(CardCreateParams.Type.SINGLE_USE)
    .build()
val card: Card = client.cards().create(params)

The asynchronous client supports the same options as the synchronous one, except most methods are suspending.

Error handling

The SDK throws custom unchecked exception types:

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

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

• LithicIoException: I/O networking errors.

• LithicInvalidDataException: 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.

• LithicException: 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

For methods that return a paginated list of results, this library provides convenient ways 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, you can use autoPager, which automatically handles fetching more pages for you:

Synchronous

import com.lithic.api.models.Card
import com.lithic.api.models.CardListPage

// As a Sequence:
client.cards().list(params).autoPager()
    .take(50)
    .forEach { card -> print(card) }

Asynchronous

// As a Flow:
asyncClient.cards().list(params).autoPager()
    .take(50)
    .collect { card -> print(card) }

Manual pagination

If none of the above helpers meet your needs, you can also manually request pages one-by-one. A page of results has a data() method to fetch the list of objects, as well as top-level response and other methods to fetch top-level data about the page. It also has methods hasNextPage, getNextPage, and getNextPageParams methods to help with pagination.

import com.lithic.api.models.Card
import com.lithic.api.models.CardListPage

val page = client.cards().list(params)
while (page != null) {
    for (card in page.data) {
        print(card)
    }

    page = page.getNextPage()
}

Logging

The SDK uses the standard OkHttp logging interceptor.

Enable logging by setting the LITHIC_LOG environment variable to info:

$ export LITHIC_LOG=info

Or to debug for more verbose logging:

$ export LITHIC_LOG=debug

Webhook Verification

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

You can use lithic.webhooks().verifySignature(body, headers, secret?) or lithic.webhooks().unwrap(body, headers, secret?), both of which will raise an error 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). The .unwrap() method can parse this JSON for you.

Network options

Retries

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

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 response.

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

import com.lithic.api.client.LithicClient
import com.lithic.api.client.okhttp.LithicOkHttpClient

val client: LithicClient = LithicOkHttpClient.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:

import com.lithic.api.models.Card
import com.lithic.api.models.CardCreateParams

val card: Card = client.cards().create(
  params, RequestOptions.builder().timeout(Duration.ofSeconds(30)).build()
)

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

import com.lithic.api.client.LithicClient
import com.lithic.api.client.okhttp.LithicOkHttpClient
import java.time.Duration

val client: LithicClient = LithicOkHttpClient.builder()
    .fromEnv()
    .timeout(Duration.ofSeconds(30))
    .build()

Proxies

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

import com.lithic.api.client.LithicClient
import com.lithic.api.client.okhttp.LithicOkHttpClient
import java.net.InetSocketAddress
import java.net.Proxy

val client: LithicClient = LithicOkHttpClient.builder()
    .fromEnv()
    .proxy(Proxy(
      Proxy.Type.HTTP, InetSocketAddress(
        "https://example.com", 8080
      )
    ))
    .build()

Environments

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

import com.lithic.api.client.LithicClient
import com.lithic.api.client.okhttp.LithicOkHttpClient

val client: LithicClient = LithicOkHttpClient.builder()
    .fromEnv()
    .sandbox()
    .build()

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:

import com.lithic.api.core.JsonValue
import com.lithic.api.models.CardCreateParams

val params: CardCreateParams = CardCreateParams.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. You can also set undocumented parameters on nested headers, query params, or body classes using the putAdditionalProperty method. These properties can be accessed on the built object later using the _additionalProperties() method.

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

import com.lithic.api.core.JsonValue
import com.lithic.api.models.CardCreateParams

val params: CardCreateParams = CardCreateParams.builder()
    .type(JsonValue.from(42))
    .build()

Response properties

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

import com.lithic.api.core.JsonBoolean
import com.lithic.api.core.JsonNull
import com.lithic.api.core.JsonNumber
import com.lithic.api.core.JsonValue

val additionalProperties: Map<String, JsonValue> = client.cards().create(params)._additionalProperties()
val secretPropertyValue: JsonValue = additionalProperties.get("secretProperty")

val result = when (secretPropertyValue) {
    is JsonNull -> "It's null!"
    is JsonBoolean -> "It's a boolean!"
    is JsonNumber -> "It's a number!"
    // Other types include `JsonMissing`, `JsonString`, `JsonArray`, and `JsonObject`
    else -> "It's something else!"
}

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

import com.lithic.api.core.JsonField
import com.lithic.api.models.CardCreateParams

val type: JsonField<CardCreateParams.Type> = client.cards().create(params)._type()

if (type.isMissing()) {
  // The property is absent from the JSON response
} else if (type.isNull()) {
  // The property was set to literal null
} else {
  // Check if value was provided as a string
  // Other methods include `asNumber()`, `asBoolean()`, etc.
  val jsonString: String? = type.asString();

  // Try to deserialize into a custom type
  val myObject: MyClass = type.asUnknown()!!.convert(MyClass::class.java)
}

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 LithicInvalidDataException only if you directly access the property.

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

import com.lithic.api.models.Card

val card: Card = client.cards().create(params).validate()

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

import com.lithic.api.models.Card
import com.lithic.api.models.CardCreateParams

val card: Card = client.cards().create(
  params, RequestOptions.builder().responseValidation(true).build()
)

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

import com.lithic.api.client.LithicClient
import com.lithic.api.client.okhttp.LithicOkHttpClient

val client: LithicClient = LithicOkHttpClient.builder()
    .fromEnv()
    .responseValidation(true)
    .build()

FAQ

Why don't you use plain enum classes?

Kotlin 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.