Open Source Java Libraries

With 50+ client generators, you can easily generate code to interact with any server which exposes an OpenAPI document. Maintainers of APIs may also automatically generate and distribute clients as part of official SDKs. Each client supports different options and features, but all templates can be replaced with your own Mustache-based templates. Getting started with server development can be tough, especially if you're evaluating technologies. We can reduce the burden when you bring your own OpenAPI document. Some generators support Inversion of Control, allowing you to iterate on design via your OpenAPI document without worrying about blowing away your entire domain layer when you regenerate code. Ever wanted to iteratively design a MySQL database, but writing table declarations was too tedious? OpenAPI documents allow you to convert the metadata about your API into some other format.

OpenAI-Java is the official Java client library provided by OpenAI for interacting with the OpenAI API. It is designed to make it easier for Java applications to call endpoints like chat completions, embeddings, function calling, streaming, and other model services using idiomatic Java patterns. You configure the client (often via environment variables or system properties), then build parameter objects (e.g. ChatCompletionCreateParams) and invoke methods like client.chat().completions().create(...) to send requests in a type-safe way. The library also supports streaming APIs, where the response arrives in chunks, using helpers like ChatCompletionAccumulator to accumulate partial responses into a full object. For complex use cases (e.g. structured outputs, function calling), it provides schema support, JSON annotations, and schema validation.

Swagger Core is a Java implementation of the OpenAPI Specification. Current version supports JAX-RS2 (javax and jakarta namespaces). One of the common usage scenarios is to integrate swagger-jaxrs2 into an existing or new JAX-RS based project ("code-first"), to automatically provide and expose its APIs definition, which is kept in sync during the project lifecycle. Such definition can be the base for further processing/consumption, including API documentation (e.g with swagger-ui, API client generation in various languages (e.g with swagger-codegen), custom processing, and so on. Such result is achieved by scanning JAX-RS resources and resolving their operations and used types, (also) processing applied annotations (e.g. Swagger, JAX-RS, Jackson, JAXB, etc.). An extension mechanism allows to further customize and pre/post processing result.