Skip to content

Official Kotlin SDK for interacting with the WorkOS API

License

Notifications You must be signed in to change notification settings

workos/workos-kotlin

Repository files navigation

WorkOS Kotlin Maven Central

The WorkOS Kotlin library provides convenient access to the WorkOS API from applications written in JVM compatible languages.

Documentation

See the API Reference for Kotlin/Java usage examples.

Installation

Apache Maven

<dependency>
  <groupId>com.workos</groupId>
  <artifactId>workos</artifactId>
  <version>VERSION</version>
</dependency>

Customers using Maven who receive a "NoSuchMethodError" error referencing Fuel may need to specify a version of Kotlin greater than 1.4.0.

<properties>
    <kotlin.version>1.4.0</kotlin.version>
</properties>

Gradle (Groovy DSL)

dependencies {
  implementation 'com.workos:workos:VERSION'
}

Gradle (Kotlin DSL)

dependencies {
  implementation("com.workos:workos:VERSION")
}

Use

import com.workos.WorkOS;

WorkOS workos = new WorkOS("WORKOS_API_KEY");

// Access different domains of the WorkOS API through the following properties
// workos.directorySync
// workos.organizations
// workos.passwordless
// workos.portal
// workos.sso
// workos.userManagement
// workos.webhooks

SDK Versioning

For our SDKs WorkOS follows a Semantic Versioning (SemVer) process where all releases will have a version X.Y.Z (like 1.0.0) pattern wherein Z would be a bug fix (e.g., 1.0.1), Y would be a minor release (1.1.0) and X would be a major release (2.0.0). We permit any breaking changes to only be released in major versions and strongly recommend reading changelogs before making any major version upgrades.

See full examples at https://github.com/workos-inc/java-example-applications.

Beta Releases

WorkOS has features in Beta that can be accessed via Beta releases. We would love for you to try these and share feedback with us before these features reach general availability (GA). To install a Beta version, please follow the installation steps above using the Beta release version.

Note: there can be breaking changes between Beta versions. Therefore, we recommend pinning the package version to a specific version. This way you can install the same version each time without breaking changes unless you are intentionally looking for the latest Beta version.

We highly recommend keeping an eye on when the Beta feature you are interested in goes from Beta to stable so that you can move to using the stable version.

More Information