Skip to main content

elody SDK for Python

Installation

To install the Python SDK library using pip:

pip install elody

Usage

Begin by importing the elody module:

import elody

Then construct a client object with the url to the elody collection service and JWT-token:

client = elody.Client(elody_collection_url=collection_url, static_jwt=jwt_token)

For production, you can specify the ELODY_COLLECTION_URL and STATIC_JWT environment variables instead of specifying the key and secret explicitly.

Examples

Creating an object

object = {
    "identifiers": ["test"],
    "type": "asset",
    "metadata": [
        {
            "key": "title",
            "value": "test",
            "lang": "en",
        }
    ]
}

client.add_object("entities", object)

Getting an object

object = client.get_object("entities", "test")
print(object)

Updating an object

object_update = {
    "identifiers": ["test"],
    "type": "asset",
    "metadata": [
        {
            "key": "title",
            "value": "test UPDATE",
            "lang": "en",
        }
    ]
}

client.update_object("entities", "test", object_update)

Deleting an object

client.delete_object("entities", "test")

Observability

pip install elody[observability] adds elody.observability: traces, metrics, logs and errors to an OpenTelemetry collector (HyperDX), for every Elody Flask service the same way.

from elody.observability import init_observability, record_exception, traced_rabbit

app = Flask(__name__)
init_observability(app)  # Flask and outgoing requests; metrics; the root logger's records
rabbit = traced_rabbit(amqpstorm_flask.RabbitMQ(...))  # before its queues are registered

Nothing is sent unless OTEL_EXPORTER_OTLP_ENDPOINT is set and OTEL_SDK_DISABLED is not true; OTEL_SERVICE_NAME names the service, OTEL_RESOURCE_ATTRIBUTES adds e.g. the client (service.namespace). A RabbitMQ message carries the trace (W3C traceparent) and the request's elody.* baggage (the pseudonymous user, library and browser session, set by the GraphQL server) to its consumer, whose spans name them. record_exception(error) records an unexpected error (not a 4xx, not a missing entity) on the current span.

Tests: pip install -e .[observability] pytest && pytest tests.

Metadata

Release files for elody 0.0.270

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

Source distribution (sdist)

Source distribution for elody 0.0.270
File Size Uploaded Provenance Actions
elody-0.0.270.tar.gz 65.5 kB With provenance Details for elody-0.0.270.tar.gz

Built distribution (wheel)

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

Total release size: 141.5 kB

Release files / elody-0.0.270.tar.gz

Download URL elody-0.0.270.tar.gz
Size 65.5 kB
Tags Source
SHA-256 checksum
How to use checksums
99c38988a3816d3a9419351afa87ddc4b4d5b50404d029ab9306741d707bbc5c
BLAKE2b-256 checksum
How to use checksums
218b2c5332abb66780ce45794a1a656221996f7305f7afc2268bc73f5618923a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Release files / elody-0.0.270-py3-none-any.whl

Download URL elody-0.0.270-py3-none-any.whl
Size 76.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c85acd1cfb44230bf1d34141c31487540c76179b04dc435af386fa0899ee892a
BLAKE2b-256 checksum
How to use checksums
ee8c339fb4bbbd53594ec0bf9f3ddd92f7ebbf3bb2c9e4c81019f72b7e40ed9d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Security for elody 0.0.270

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for elody-0.0.270.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

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

0.0.270 This release

2 release files Full provenance

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