engini-client
Autogenerated Python REST client for the Engini Public API
("DeveloperAPI", /v1) — a thin transport layer built on attrs + httpx.
This is the base client layer of Engini's two-package SDK stack. For an ergonomic,
agent-first interface (typed errors, retry/backoff, auto-pagination, LLM tool wrapping), use
the higher-level engini SDK that's built on top of this.
The code under
engini_client/is generated from an OpenAPI spec and committed — it is not hand-edited. See the repository to regenerate.
Install
pip install engini-client
Usage
from engini_client import AuthenticatedEnginiClient
from engini_client.api.connections import connections_get_connections # example op
client = AuthenticatedEnginiClient(
base_url="https://api.engini.io", # requests append /v1/...
token="<JWT>", # → Authorization: Bearer <JWT>
)
result = connections_get_connections.sync(client=client)
Source & docs: https://github.com/engini/engini-client
Metadata
Release files for engini-client 0.12.0
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 |
|---|---|---|---|---|
| engini_client-0.12.0.tar.gz | 102.0 kB | With provenance | Details for engini_client-0.12.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| engini_client-0.12.0-py3-none-any.whl | Python 3 | none | any | Details for engini_client-0.12.0-py3-none-any.whl |
Total release size: 395.5 kB
Release files / engini_client-0.12.0.tar.gz
| Download URL | engini_client-0.12.0.tar.gz |
|---|---|
| Size | 102.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae0401578c758cf244a32493f7c2cdec717f2bc3aa400f9fa9a7da4016fe5e31
|
|
BLAKE2b-256 checksum How to use checksums |
f6ecb73b1640216e153a365f630bf64a1301fe7ec37b33940eee10b648557f4b
|
| 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 4, 2026.
Transparency logRelease files / engini_client-0.12.0-py3-none-any.whl
| Download URL | engini_client-0.12.0-py3-none-any.whl |
|---|---|
| Size | 293.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
16b218027447245186e498cd0b7765db8fc56c9b6a804a610c830523a50220e6
|
|
BLAKE2b-256 checksum How to use checksums |
b95ed3e0d65a249620390d3ac79aed766023fe8d4188d02d2dc7790c09b44241
|
| 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 4, 2026.
Transparency logSecurity for engini-client 0.12.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
Both files in this release have been uploaded with provenance metadata.
Attestation for engini_client-0.12.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 4, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.