tigrbl_client
Typed Python client for Tigrbl REST and JSON-RPC APIs with sync and async calls, nested resource helpers, and optional Pydantic validation.
What is tigrbl_client?
Typed Python client for Tigrbl REST and JSON-RPC APIs with sync and async calls, nested resource helpers, and optional Pydantic validation.
Why use tigrbl_client?
Use it when a Python service or test suite needs a typed client for Tigrbl REST and JSON-RPC APIs.
When should I install tigrbl_client?
Install it in consumers, integration tests, SDK adapters, and automation that calls an already-running Tigrbl service.
Who is tigrbl_client for?
Client authors, API consumers, QA engineers, and service integration teams.
Where does tigrbl_client fit?
tigrbl_client lives at pkgs/95_client/tigrbl_client and serves calling Tigrbl services from Python clients and tests.
How does tigrbl_client work?
It wraps HTTP calls with sync and async helpers, optional API-key headers, REST CRUD helpers, JSON-RPC calls, and nested-resource helpers.
Install
uv add tigrbl_client
pip install tigrbl_client
Surface Coverage
| Surface | Value |
|---|---|
| PyPI package | tigrbl_client |
| Repository path | pkgs/95_client/tigrbl_client |
| Python import root | tigrbl_client |
| Console scripts | none declared |
| Entry points | none declared |
| Optional extras | none declared |
| Legal files | LICENSE, NOTICE |
| Supported Python | `3.10 |
What It Owns
tigrbl_client owns the client package boundary. It should be installed when you need this package's focused responsibility without assuming every other Tigrbl workspace package is present.
Implementation orientation:
tigrbl_client: _crud, _nested_crud, _rpc
Public API and Import Surface
- Import roots:
tigrbl_client. - Public symbols:
NestedCRUDMixin,TigrblClient,_Schema. - Workspace dependencies: none declared.
- External runtime dependencies:
httpx>=0.27.0,pydantic>=2.0.0.
Usage Examples
Verify the installed package
python -m pip show tigrbl_client
python - <<'PY'
from importlib.metadata import version
print(version("tigrbl_client"))
PY
Call REST endpoints
from tigrbl_client import TigrblClient
with TigrblClient("https://api.example.com") as client:
item = client.get("/items/1")
created = client.post("/items", data={"name": "example"})
Call JSON-RPC endpoints
from tigrbl_client import TigrblClient
client = TigrblClient("https://api.example.com/rpc")
result = client.call("items.get", params={"id": 1})
Use async helpers
from tigrbl_client import TigrblClient
async with TigrblClient("https://api.example.com") as client:
item = await client.aget("/items/1")
How To Choose This Package
Choose tigrbl_client when the quick-answer table matches your use case. Choose tigrbl instead when you want the full public facade. Choose a lower-level package such as tigrbl-core, tigrbl-base, or tigrbl-runtime when you are building framework extensions or testing a specific internal boundary.
Related Packages
Documentation Links
- Workspace docs
- Package catalog
- Package layout
- Current target
- Current state
- SSOT registry
- Release workflow
Support
- Community: Discord.
- Issues: GitHub Issues.
- Repository: pkgs/95_client/tigrbl_client.
Package-local Boundary
This README is the package-local distribution entry point for tigrbl_client. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.
Certification Status
- Package status: governed package in the
tigrbl/tigrblworkspace. - Governance source: SSOT registry.
- Release evidence: publish workflow validates package builds, tests, GitHub release assets, and PyPI publication for managed packages.
- Local certification guard:
pkgs/97_tests/tigrbl_tests/tests/unit/test_package_badges_and_notices.pyverifies every package README keeps the Discord badge, Apache 2.0 badge, explicit Python-version badge,LICENSE, andNOTICE. - Scope note: this README documents the package boundary. Runtime feature support remains governed by
.ssot/entities and the conformance docs linked below.
License
Licensed under the Apache License, Version 2.0. See LICENSE, NOTICE, and the official Apache 2.0 license text.
Metadata
Release files for tigrbl_client 0.4.5
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 | Actions |
|---|---|---|---|---|
| tigrbl_client-0.4.5.tar.gz | 18.5 kB | Without provenance | Details for tigrbl_client-0.4.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tigrbl_client-0.4.5-py3-none-any.whl | Python 3 | none | any | Details for tigrbl_client-0.4.5-py3-none-any.whl |
Total release size: 36.7 kB
Release files / tigrbl_client-0.4.5.tar.gz
| Download URL | tigrbl_client-0.4.5.tar.gz |
|---|---|
| Size | 18.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
853e2e4fa923441f45fdfc9d13f8d03c7d9736642e9fd36d5f39546988b5d0b4
|
|
BLAKE2b-256 checksum How to use checksums |
23b249f5b44f4e2e06acd7579a54f11fd60c98a3fa98f4a01cf45c6301576e4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tigrbl_client-0.4.5-py3-none-any.whl
| Download URL | tigrbl_client-0.4.5-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34408d89a61fe2aa762ef3c476513ca45cfb79119528e358bac7193046b88820
|
|
BLAKE2b-256 checksum How to use checksums |
5efa18068db8796df0f919dadf412f8255105ee3e097676936723c0f8748ede7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tigrbl_client 0.4.5
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.