Skip to main content

RTLS SDK

A Python SDK for the RTLS REST API.

📖 Documentation: https://rtls-sdk.pages.dev

Three-step usage:

from rtls_sdk import RtlsClient

client = RtlsClient.from_env()
tags = client.tags.list()

That's it — token, refresh, scoping headers, 401 re-login are all internal. The first method call performs a lazy login; subsequent calls reuse the session.

What you get

  • Compound workflows. One Python call replaces the multi-call REST sagas the JS reference client makes you script — e.g. tags.create(name="X", attached_zone="Z", groups=[...]) runs the three-step create-and-attach with rollback on partial failure.
  • One exception hierarchy. Everything under RtlsError: NotFound, ValidationError, RateLimited, ServerError, PartialFailureError, ReportFailed / ReportTimeout, …
  • Typed models. Pydantic v2 under the hood; mypy --strict clean out of the box; ships py.typed.
  • Mandatory redaction. No password, token, refresh-token, cookie, or Authorization header ever reaches a log handler. There is no opt-out flag.
  • Live streaming. client.ws opens a WebSocket subscription and yields typed channel messages (positions, alarms, zone events, …).
  • Sync-only for v1. The async surface is on the v2 roadmap.

Install

pip install rtls-sdk

Python 3.10+ supported. See docs/install.md for dev install and verification.

Quickstart

export RTLS_USERNAME="qa@example.com"
export RTLS_PASSWORD="hunter2"
export RTLS_BASE_URL="https://rtls.example.com"
from rtls_sdk import RtlsClient

with RtlsClient.from_env() as client:
    for tag in client.tags.list():
        print(tag.uid, tag.name)

For the full 5-minute walkthrough see docs/quickstart.md.

Documentation

Full documentation: https://rtls-sdk.pages.dev

  • Install · Quickstart
  • Entity catalog — one page per entity (tags, sites, areas, floorplans, anchors, zones, nodes, users, reports, …) with methods, examples, and model fields.
  • Guides — compound workflows, error handling, pagination, rate limiting, scope switching, timestamps, reports, floorplans, credential rotation.
  • Advanced — BYO token, raw REST methods, logging, HTTP client override, security.
  • Migrating from the JS client, plus an API reference auto-generated from docstrings.

Status

v0.6.2. See CHANGELOG.md for the full release history — including the 0.6.0 breaking changes to the LSB orchestration surface (update → save, no-arg start() / stop() returning bool) and the Association → TagAssociation rename (client.associations is now client.tag_associations).

License

MIT — see LICENSE.

Metadata

Release files for rtls-sdk 0.7.0

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

Source distribution (sdist)

Source distribution for rtls-sdk 0.7.0
File Size Uploaded Provenance
rtls_sdk-0.7.0.tar.gz 115.5 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for rtls-sdk 0.7.0
File Interpreter ABI Platform
rtls_sdk-0.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 272.5 kB

Release files / rtls_sdk-0.7.0.tar.gz

Download URL rtls_sdk-0.7.0.tar.gz
Size 115.5 kB
Tags Source
SHA-256 checksum
How to use checksums
28f8e855a1ef6bcb7d4add0a666cd797a35c139bf96d100507cf9aae09c5cc84
BLAKE2b-256 checksum
How to use checksums
d6af81461558a329901bae6507aa7b284426dcb2943a74db26222d4eae9be9c6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 20, 2026.

Transparency log

Release files / rtls_sdk-0.7.0-py3-none-any.whl

Download URL rtls_sdk-0.7.0-py3-none-any.whl
Size 157.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
43a35b94584bf53ebaf888411183d979068290828b59e5a1b118dfc1e3f7aab7
BLAKE2b-256 checksum
How to use checksums
44e8f38836a8645fc2d84f231853616ea71b99d126551a5307aa2f81a6e0bb33
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 20, 2026.

Transparency log

Security for rtls-sdk 0.7.0

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

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for rtls_sdk-0.7.0.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 20, 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.

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