lippertzpy
A lightweight Python library for the Jifeline Partner API and local logging.
Simplify API requests, keep your authentication in one place, and automatically write log files next to your scripts.
Language
Features
- Easy access to the Jifeline Partner API
- Helpers for
get,post,put, anddelete - OAuth token is cached and reused until shortly before it expires
- API error messages are included in the raised exception
- Local logging via liplog
Requirements
- Python 3.10 or newer
- Valid credentials for the Jifeline Partner API
Installation
Install from PyPI:
python -m pip install lippertzpy
Install directly from GitHub:
python -m pip install git+https://github.com/R0g3rT/lippertzPy.git
Update:
python -m pip install --upgrade lippertzpy
Uninstall:
python -m pip uninstall lippertzpy
Configuration
Create a .env file in the same folder as the Python script you start and add your credentials:
client_id=your_client_id
client_secret=your_client_secret
Alternatively, set client_id and client_secret as environment variables. Existing environment variables take precedence over the .env file.
Quick start
from lippertzpy import get, post, write_log
write_log("API client started", "RUN")
ticket = get("tickets/tickets/123")
result = post("endpoint", {"key": "value"})
write_log("Done", "SUCCESS")
Supported API methods
get(endpoint)post(endpoint, data)put(endpoint, data)delete(endpoint)
data is sent as JSON. Empty responses (e.g. 204 No Content) return {}.
On HTTP errors a requests.HTTPError is raised that contains the status code and the response text of the API.
Logging
write_log and setup_logging come from liplog.
Supported levels: DEBUG, RUN, INFO, SUCCESS, WARNING, ERROR, CRITICAL. An unknown level raises a ValueError.
Log files are stored in logs/<script>/ next to the Python script that was started. The folder is created on the first log entry.
Changes in 0.3.0
- Requires
liplog>=0.3.0: log files are stored inlogs/<script>/,DEBUGis supported, console output goes to stdout
Changes in 0.2.0
- Logging now uses
liplog: the log folder islogs(previouslylog) write_log(message, level="INFO"): theretriesanddelay_msparameters were removed- Requires Python 3.10 or newer
Metadata
Release files for lippertzpy 0.3.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 |
|---|---|---|---|---|
| lippertzpy-0.3.0.tar.gz | 4.4 kB | With provenance | Details for lippertzpy-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lippertzpy-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for lippertzpy-0.3.0-py3-none-any.whl |
Total release size: 9.1 kB
Release files / lippertzpy-0.3.0.tar.gz
| Download URL | lippertzpy-0.3.0.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9b6784f4923d137ee47b1b71f1f7747fc579937baaec3b5ec1496b7cc4739ae
|
|
BLAKE2b-256 checksum How to use checksums |
c5d5a98c57f5726b301b5133781be68bcc6e7b31766aad3b815d3a4289744f7c
|
| 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 Nov 4, 2026.
Transparency logRelease files / lippertzpy-0.3.0-py3-none-any.whl
| Download URL | lippertzpy-0.3.0-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e66b571d0fd6ee75c1eb677d198b0d5ec348de412b6199a68c1da6853e20225
|
|
BLAKE2b-256 checksum How to use checksums |
6df0d7f98e2a064eb531432efe0e4351acd33b8d3512bad668fc9d84d559ba28
|
| 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 Nov 4, 2026.
Transparency logSecurity for lippertzpy 0.3.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.
Attestation for lippertzpy-0.3.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 Nov 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.