Python Library
The official Python library wraps the whole Ollang integration API — projects, uploads, orders, folders, revisions, translation memories, custom instructions, content, billing, locales and Figma — in a simple, Pythonic client. Source code lives in thepython/ directory of the SDK repository.
Installation
requests.
Authentication
- Sign up or log in at Olabs
- Create or select a project
- 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. A path supplies it; raw bytes and in-memory streams do not, so passfilename alongside them:
name is the display name for the created project; it does not need an
extension of its own.
Uploading VTT subtitles
Passproject_id and name instead of the old order_id argument. The API
attaches subtitles to a project and returns projectId; source language
defaults to the project’s language.
Resources
All methods return the parsed JSON response as plain dicts and lists. Non-2xx responses raise
ollang.OllangAPIError, which carries status_code and the parsed error body.
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
create_by_url 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 rawbytes. Each has a ..._to_file companion
that writes the workbook to a path, creating parent directories as needed.
The underlying HTTP client stays available for anything not wrapped yet:
client.client.get("/integration/orders"). See the full API
reference for every endpoint.