Do I have to configure the client style for Java?

No. class-namespaced is already the default, which is the client object a Java caller expects. The functions override exists, but on a language with no free functions it generates statics that read like a C API, so it is rarely what you want here.

Is there a Kotlin client too?

Yes, generated separately from the same spec, and it does expose an HTTP engine choice between okhttp and ktor. Java does not.

How are errors returned?

Declared error responses become typed exceptions, so a caller catches the failure your spec documented rather than a generic one.

What sets the package version?

Your spec does. `info.version` is propagated into the generated manifests on every build, so the version on the registry and the version in your OpenAPI document agree. A version edited inside a generated package.json or pyproject.toml is overwritten on the next build.

What happens when the spec changes?

The client is regenerated and rescored. Which changes break your users is worth knowing before you publish: a new required parameter and a renamed operationId are both breaking, because the method signature and the method name come straight from the document.

Yes. It is published to the registry under your account and your package name, and you can read the whole thing before it goes out. Nothing in it phones home unless a consumer turns error reporting on.

Does it cost anything to try?

The free tier covers 50 endpoints and one SDK language, with a custom domain and GitHub sync included. Paid tiers start at $49 a month and bundle more languages.

JavaSDK generation

Generate a Java SDK from your OpenAPI spec

Octri reads your OpenAPI document and writes a Java client with typed models, publishes it to Maven Central under a groupId you control, and rebuilds it every time the spec changes.

Generate one free Score my spec first

install · Maven Central

<dependency>
  <groupId>com.acme</groupId>
  <artifactId>api-client</artifactId>
  <version>1.0.0</version>
</dependency>

The client they actually get

What your users write once the Java package is installed.

Two call-site shapes come out of the same spec. class-namespaced is the default: a client object whose operations are grouped by resource, which is the surface every widely used SDK ships and the one your own reference docs already assume. functions is the override, and it is the one to reach for when your users care about tree-shaking. It is a single setting, per language, and nothing else about the client changes with it.

Requests are builders either way, so a new optional parameter never breaks a call site that already compiles.

Coordinates are groupId:artifactId, and Maven Central verifies that the groupId is a domain you control. That check is a one-off, and it is the part of a first Java release that takes the longest.

The Java guide, in full

java · class-namespaced (default)

var config = new SdkConfig.ClientConfig();
config.baseUrl = "https://api.acme.com/v1";
var auth = new SdkConfig.ClientAuthConfig();
auth.bearerAuth = System.getenv("ACME_TOKEN");
config.auth = auth;

var acme = new Acme(config);

// Namespaces are final fields on the client, not accessor methods.
acme.users.listPaginated(
    ListUsersRequest.builder().limit(100).build(),
    user -> {
        System.out.println(user.getId());
        return true;
    });

java · functions

SdkConfig.configureClient(config);

Users.listUsersPaginated(
    ListUsersRequest.builder().limit(100).build(),
    user -> {
        System.out.println(user.getId());
        return true;
    });

What you decide for Java

Java exposes no HTTP engine setting. Kotlin offers okhttp and ktor; Java uses java.net.http.HttpClient.

Client style
class-namespaced (default), class, namespaced, functions
A client object with a field per resource, which is what a Java caller expects. The functions style maps awkwardly onto a language with no free functions, so it is an override you are unlikely to want here.
Argument style
object (default), positional
The object style is a request builder, the JVM convention for anything with optional fields. Positional becomes an overload set that grows with your spec.
Method naming
short (default), full
Short strips the namespace word, so getBalance under balance becomes balance.get().
Namespace
tags (default), path
Tags decide whether a caller writes acme.invoices.list() or acme.v1.list(). Namespaces are final fields on the client, not accessors.
Doc comments
full (default), minimal
Full carries your spec’s prose into the Javadoc an IDE shows on hover.

Decide this before the first release

Maven Central verifies your groupId

The groupId has to be a domain you actually control, and Sonatype checks it before your first release rather than after. com.acme means proving you own acme.com. Start that verification before you plan the release, because it is the one step in a Java launch that is not in your hands.

In every generated client, not just this one

The parts nobody wants to hand-write, and the parts a hand-written client usually skips.

Retries with exponential backoff and jitter, on the statuses that mean "try again", with a per-attempt timeout.
Idempotency keys on the methods that need them, so a retried write does not become two.
Auth wired in from your spec’s security scheme, read from wherever your users keep secrets.
Typed errors split by cause: a failed constraint, an HTTP status, a network failure and a timeout are four different things.
Pagination that follows whichever contract your spec declares, cursor, offset, page number or next URL, without prefetching the collection.
Server-sent events as a native stream, for the operations that stream.
Error reporting to Octri’s monitoring, pre-wired and switched off until a consumer opts in.

How SDK Studio shapes a client

Point it at your spec
Upload an OpenAPI or Swagger document, paste a URL, or connect the repository it lives in so a merge to main updates it.
Read the audit
The spec is scored out of 10 on what a generator can do with it, with every missing schema and colliding operationId named. 9 of the fourteen rules carry a button that writes the fix.
Shape the client
Client style, argument style, namespacing, auth, retries and pagination, set once for the project and overridden per language or per endpoint.
Generate and read it
The package is generated, compiled and handed to you as source you can read before anyone installs it.
Publish, then keep publishing
Release to the registry under your own account. Every later spec change regenerates the client, and the version comes from your document rather than from us.

Or in another language

One spec, ten languages. These three are generated from the same document, with the same settings, at the same time.

TypeScript

Published to npm.

OpenAPI to TypeScript

Python

Published to PyPI.

OpenAPI to Python

Published to a git tag.

OpenAPI to Go

Questions

Either. The package is published to Maven Central, and both build tools resolve from it. The README carries the coordinates in both forms.