Skip to main content

Java Library

The official Java library wraps the whole Ollang integration API — projects, uploads, orders, folders, revisions, translation memories, custom instructions, content, billing, locales and Figma — using the JDK’s built-in HTTP client, with Gson as the only runtime dependency. Source code lives in the java/ directory of the SDK repository. Requires Java 11+.

Installation

Maven:
Gradle:

Authentication

  1. Sign up or log in at Olabs
  2. Create or select a project
  3. Generate an API key from project settings

Quick Start

Naming the uploaded file

The platform takes the stored file’s extension from the name the file is sent under, and rejects an upload it cannot get one from. The Path overloads use the file’s own name; the in-memory overload takes it as an argument:
The third argument is the display name for the created project; it does not need an extension of its own.

Uploading VTT subtitles

The VTT overloads take a source project ID and a display name, replacing the old order ID argument. Source language comes from the project; the response contains projectId.

Resources

All methods return the parsed JSON response as a Gson JsonElement. Non-2xx responses throw OllangApiException, which carries the HTTP status code and the response body (raw and parsed).

More Examples

Resolve a language code

Order and project creation match language codes exactly, so resolve anything uncertain instead of guessing at a region subtag.

Translation memories

Folders

Billing

Large remote files

createByUrl hands the platform a URL to fetch server-side, so the bytes never pass through your process and there is no practical size ceiling.

XLSX exports

The export endpoints return raw bytes. Each has a ...ToFile companion that writes the workbook to a path, creating parent directories as needed.
The underlying HTTP client stays available for anything not wrapped yet: ollang.client().get("/integration/orders"). See the full API reference for every endpoint.