SDKs Overview
The official DocLD SDKs give you a typed, idiomatic way to call the DocLD API from your application. Use them instead of raw HTTP when you want a single client, consistent error handling, and full TypeScript or Python types.
Available SDKs
| Language | Package | Docs |
|---|---|---|
| JavaScript / TypeScript | docld (npm) | JavaScript |
| Python | docld (PyPI) | Python |
Each SDK supports the same core surface: upload, parse, documents (list, get, delete, getParse, getStatus), and extract (run extraction, manage schemas). Configuration uses an API key and optional base URL (or environment variables).
When to use what
| Approach | Best for |
|---|---|
| SDK (JS or Python) | Application code (server or client), scripts, backends. Typed client, one-line config, consistent errors. |
| REST API (curl / fetch) | Quick one-off calls, custom stacks, or when you prefer no dependencies. See API Quickstart and API Reference. |
| CLI | Command-line workflows (parse folders, extract with a schema file). See CLI Overview. |
Next steps
- JavaScript SDK — Installation, configuration, and full API reference for the Node.js/browser SDK.
- Python SDK — Installation, configuration, and full API reference for the Python SDK.
- API Reference — Full REST endpoint documentation for all DocLD capabilities.
Last updated on