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 --strictclean out of the box; shipspy.typed. - Mandatory redaction. No password, token, refresh-token, cookie,
or
Authorizationheader ever reaches a log handler. There is no opt-out flag. - Live streaming.
client.wsopens 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.6.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| rtls_sdk-0.6.3.tar.gz | 113.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rtls_sdk-0.6.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 268.9 kB
Release files / rtls_sdk-0.6.3.tar.gz
| Download URL | rtls_sdk-0.6.3.tar.gz |
|---|---|
| Size | 113.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f039d3408a4fb7459fb5c7243469dc869b7dffc671cc5c06df8acf104af27263
|
|
BLAKE2b-256 checksum How to use checksums |
953e26f744926924fc7511c3157d396e447dc4e8b06b47551bfb3a5ef4bccf3a
|
| 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 Sep 10, 2026.
Transparency logRelease files / rtls_sdk-0.6.3-py3-none-any.whl
| Download URL | rtls_sdk-0.6.3-py3-none-any.whl |
|---|---|
| Size | 155.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8fe41fb18201d7a1b33b2b349e5cd883f553f71a8f6f1caecc8cb668a1adf51b
|
|
BLAKE2b-256 checksum How to use checksums |
dc5583d7a0c69b33f6738cd70df283d5ba9e29e5f67a742a918e7f39f89633db
|
| 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 Sep 10, 2026.
Transparency logSecurity for rtls-sdk 0.6.3
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.
Attestation for rtls_sdk-0.6.3.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 Sep 10, 2026.
Transparency logA 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.