Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Dataleon Python API library

PyPI version

The Dataleon Python library provides convenient access to the Dataleon REST API from any Python 3.9+ application. The library includes type definitions for all request params and response fields, and offers both synchronous and asynchronous clients powered by httpx.

It is generated with Stainless.

MCP Server

Use the Dataleon MCP Server to enable AI assistants to interact with this API, allowing them to explore endpoints, make test requests, and use documentation to help integrate this SDK into your application.

Add to Cursor Install in VS Code

Note: You may need to set environment variables in your MCP client.

Documentation

The REST API documentation can be found on docs.dataleon.ai. The full API of this library can be found in api.md.

Installation

# install from PyPI
pip install '--pre dataleon'

Usage

The full API of this library can be found in api.md.

import os
from dataleon import Dataleon

client = Dataleon(
    api_key=os.environ.get("DATALEON_API_KEY"),  # This is the default and can be omitted
)

individual = client.individuals.create(
    workspace_id="wk_123",
)
print(individual.id)

While you can provide an api_key keyword argument, we recommend using python-dotenv to add DATALEON_API_KEY="My API Key" to your .env file so that your API Key is not stored in source control.

Async usage

Simply import AsyncDataleon instead of Dataleon and use await with each API call:

import os
import asyncio
from dataleon import AsyncDataleon

client = AsyncDataleon(
    api_key=os.environ.get("DATALEON_API_KEY"),  # This is the default and can be omitted
)


async def main() -> None:
    individual = await client.individuals.create(
        workspace_id="wk_123",
    )
    print(individual.id)


asyncio.run(main())

Functionality between the synchronous and asynchronous clients is otherwise identical.

With aiohttp

By default, the async client uses httpx for HTTP requests. However, for improved concurrency performance you may also use aiohttp as the HTTP backend.

You can enable this by installing aiohttp:

# install from PyPI
pip install '--pre dataleon[aiohttp]'

Then you can enable it by instantiating the client with http_client=DefaultAioHttpClient():

import os
import asyncio
from dataleon import DefaultAioHttpClient
from dataleon import AsyncDataleon


async def main() -> None:
    async with AsyncDataleon(
        api_key=os.environ.get("DATALEON_API_KEY"),  # This is the default and can be omitted
        http_client=DefaultAioHttpClient(),
    ) as client:
        individual = await client.individuals.create(
            workspace_id="wk_123",
        )
        print(individual.id)


asyncio.run(main())

Using types

Nested request parameters are TypedDicts. Responses are Pydantic models which also provide helper methods for things like:

  • Serializing back into JSON, model.to_json()
  • Converting to a dictionary, model.to_dict()

Typed requests and responses provide autocomplete and documentation within your editor. If you would like to see type errors in VS Code to help catch bugs earlier, set python.analysis.typeCheckingMode to basic.

Nested params

Nested parameters are dictionaries, typed using TypedDict, for example:

from dataleon import Dataleon

client = Dataleon()

individual = client.individuals.create(
    workspace_id="wk_123",
    person={},
)
print(individual.person)

File uploads

Request parameters that correspond to file uploads can be passed as bytes, or a PathLike instance or a tuple of (filename, contents, media type).

from pathlib import Path
from dataleon import Dataleon

client = Dataleon()

client.individuals.documents.upload(
    individual_id="individual_id",
    document_type="liasse_fiscale",
    file=Path("/path/to/file"),
)

The async client uses the exact same interface. If you pass a PathLike instance, the file contents will be read asynchronously automatically.

Handling errors

When the library is unable to connect to the API (for example, due to network connection problems or a timeout), a subclass of dataleon.APIConnectionError is raised.

When the API returns a non-success status code (that is, 4xx or 5xx response), a subclass of dataleon.APIStatusError is raised, containing status_code and response properties.

All errors inherit from dataleon.APIError.

import dataleon
from dataleon import Dataleon

client = Dataleon()

try:
    client.individuals.create(
        workspace_id="wk_123",
    )
except dataleon.APIConnectionError as e:
    print("The server could not be reached")
    print(e.__cause__)  # an underlying Exception, likely raised within httpx.
except dataleon.RateLimitError as e:
    print("A 429 status code was received; we should back off a bit.")
except dataleon.APIStatusError as e:
    print("Another non-200-range status code was received")
    print(e.status_code)
    print(e.response)

Error codes are as follows:

Status Code Error Type
400 BadRequestError
401 AuthenticationError
403 PermissionDeniedError
404 NotFoundError
422 UnprocessableEntityError
429 RateLimitError
>=500 InternalServerError
N/A APIConnectionError

Retries

Certain errors are automatically retried 2 times by default, with a short exponential backoff. Connection errors (for example, due to a network connectivity problem), 408 Request Timeout, 409 Conflict, 429 Rate Limit, and >=500 Internal errors are all retried by default.

You can use the max_retries option to configure or disable retry settings:

from dataleon import Dataleon

# Configure the default for all requests:
client = Dataleon(
    # default is 2
    max_retries=0,
)

# Or, configure per-request:
client.with_options(max_retries=5).individuals.create(
    workspace_id="wk_123",
)

Timeouts

By default requests time out after 1 minute. You can configure this with a timeout option, which accepts a float or an httpx.Timeout object:

from dataleon import Dataleon

# Configure the default for all requests:
client = Dataleon(
    # 20 seconds (default is 1 minute)
    timeout=20.0,
)

# More granular control:
client = Dataleon(
    timeout=httpx.Timeout(60.0, read=5.0, write=10.0, connect=2.0),
)

# Override per-request:
client.with_options(timeout=5.0).individuals.create(
    workspace_id="wk_123",
)

On timeout, an APITimeoutError is thrown.

Note that requests that time out are retried twice by default.

Advanced

Logging

We use the standard library logging module.

You can enable logging by setting the environment variable DATALEON_LOG to info.

$ export DATALEON_LOG=info

Or to debug for more verbose logging.

How to tell whether None means null or missing

In an API response, a field may be explicitly null, or missing entirely; in either case, its value is None in this library. You can differentiate the two cases with .model_fields_set:

if response.my_field is None:
  if 'my_field' not in response.model_fields_set:
    print('Got json like {}, without a "my_field" key present at all.')
  else:
    print('Got json like {"my_field": null}.')

Accessing raw response data (e.g. headers)

The "raw" Response object can be accessed by prefixing .with_raw_response. to any HTTP method call, e.g.,

from dataleon import Dataleon

client = Dataleon()
response = client.individuals.with_raw_response.create(
    workspace_id="wk_123",
)
print(response.headers.get('X-My-Header'))

individual = response.parse()  # get the object that `individuals.create()` would have returned
print(individual.id)

These methods return an APIResponse object.

The async client returns an AsyncAPIResponse with the same structure, the only difference being awaitable methods for reading the response content.

.with_streaming_response

The above interface eagerly reads the full response body when you make the request, which may not always be what you want.

To stream the response body, use .with_streaming_response instead, which requires a context manager and only reads the response body once you call .read(), .text(), .json(), .iter_bytes(), .iter_text(), .iter_lines() or .parse(). In the async client, these are async methods.

with client.individuals.with_streaming_response.create(
    workspace_id="wk_123",
) as response:
    print(response.headers.get("X-My-Header"))

    for line in response.iter_lines():
        print(line)

The context manager is required so that the response will reliably be closed.

Making custom/undocumented requests

This library is typed for convenient access to the documented API.

If you need to access undocumented endpoints, params, or response properties, the library can still be used.

Undocumented endpoints

To make requests to undocumented endpoints, you can make requests using client.get, client.post, and other http verbs. Options on the client will be respected (such as retries) when making this request.

import httpx

response = client.post(
    "/foo",
    cast_to=httpx.Response,
    body={"my_param": True},
)

print(response.headers.get("x-foo"))

Undocumented request params

If you want to explicitly send an extra param, you can do so with the extra_query, extra_body, and extra_headers request options.

Undocumented response properties

To access undocumented response properties, you can access the extra fields like response.unknown_prop. You can also get all the extra fields on the Pydantic model as a dict with response.model_extra.

Configuring the HTTP client

You can directly override the httpx client to customize it for your use case, including:

import httpx
from dataleon import Dataleon, DefaultHttpxClient

client = Dataleon(
    # Or use the `DATALEON_BASE_URL` env var
    base_url="http://my.test.server.example.com:8083",
    http_client=DefaultHttpxClient(
        proxy="http://my.test.proxy.example.com",
        transport=httpx.HTTPTransport(local_address="0.0.0.0"),
    ),
)

You can also customize the client on a per-request basis by using with_options():

client.with_options(http_client=DefaultHttpxClient(...))

Managing HTTP resources

By default the library closes underlying HTTP connections whenever the client is garbage collected. You can manually close the client using the .close() method if desired, or with a context manager that closes when exiting.

from dataleon import Dataleon

with Dataleon() as client:
  # make requests here
  ...

# HTTP client is now closed

Versioning

This package generally follows SemVer conventions, though certain backwards-incompatible changes may be released as minor versions:

  1. Changes that only affect static types, without breaking runtime behavior.
  2. Changes to library internals which are technically public but not intended or documented for external use. (Please open a GitHub issue to let us know if you are relying on such internals.)
  3. Changes that we do not expect to impact the vast majority of users in practice.

We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.

We are keen for your feedback; please open an issue with questions, bugs, or suggestions.

Determining the installed version

If you've upgraded to the latest version but aren't seeing any new features you were expecting then your python environment is likely still using an older version.

You can determine the version that is being used at runtime with:

import dataleon
print(dataleon.__version__)

Requirements

Python 3.9 or higher.

Contributing

See the contributing documentation.

Metadata

Release files for dataleon 0.1.0a27

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dataleon 0.1.0a27
File Size Uploaded Provenance Actions
dataleon-0.1.0a27.tar.gz 129.9 kB Without provenance Details for dataleon-0.1.0a27.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for dataleon 0.1.0a27
File Interpreter ABI Platform Actions
dataleon-0.1.0a27-py3-none-any.whl Python 3 none any Details for dataleon-0.1.0a27-py3-none-any.whl

Total release size: 239.6 kB

Release files / dataleon-0.1.0a27.tar.gz

Download URL dataleon-0.1.0a27.tar.gz
Size 129.9 kB
Tags Source
SHA-256 checksum
How to use checksums
4dadcb21e0049f43e2bbbc29254524b03bbfd368a58d90d607ae8c3a878f8148
BLAKE2b-256 checksum
How to use checksums
d7459fbf5821576bf8e0b80816c9dbe12da6ab79513cf777f860255b296e5ad2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.12.9

Release files / dataleon-0.1.0a27-py3-none-any.whl

Download URL dataleon-0.1.0a27-py3-none-any.whl
Size 109.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
154db0c42ba13dd1441e70d150fd909deb5b9d313b9bb2f76ce0c7b660a756bb
BLAKE2b-256 checksum
How to use checksums
78e01d51fcde70760000033e4ce6fee45b4a6a7f35bab1daadf46c071cc547c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.12.9

Security for dataleon 0.1.0a27

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page