Skip to main content

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, and delete
  • 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: RUN, INFO, SUCCESS, WARNING, ERROR, CRITICAL. An unknown level raises a ValueError.

Log files are stored in a logs folder next to the Python script that was started. The folder is created on the first log entry.

Changes in 0.2.0

  • Logging now uses liplog: the log folder is logs (previously log)
  • write_log(message, level="INFO"): the retries and delay_ms parameters were removed
  • Requires Python 3.10 or newer

Metadata

Release files for lippertzpy 0.2.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 lippertzpy 0.2.0
File Size Uploaded Provenance Actions
lippertzpy-0.2.0.tar.gz 4.4 kB With provenance Details for lippertzpy-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for lippertzpy 0.2.0
File Interpreter ABI Platform Actions
lippertzpy-0.2.0-py3-none-any.whl Python 3 none any Details for lippertzpy-0.2.0-py3-none-any.whl

Total release size: 9.0 kB

Release files / lippertzpy-0.2.0.tar.gz

Download URL lippertzpy-0.2.0.tar.gz
Size 4.4 kB
Tags Source
SHA-256 checksum
How to use checksums
8c76b2b09ad9dd04dafb36a94956196a014f748557844af3937ee28b9a05c829
BLAKE2b-256 checksum
How to use checksums
c4ea268069acdc6a9ae58d4a99c00ef6e54a4341399e0d10b6174d09bd365eb8
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 3, 2026.

Transparency log

Release files / lippertzpy-0.2.0-py3-none-any.whl

Download URL lippertzpy-0.2.0-py3-none-any.whl
Size 4.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
51c01c083e925c9d826115b78b6d33e2a0ec5baa7f56d6fef1de96d98daeea99
BLAKE2b-256 checksum
How to use checksums
c456df770f5fa31e031b6a00f279d629722210b0cfbf06be52b0bd6e58bb2861
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 3, 2026.

Transparency log

Security for lippertzpy 0.2.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 lippertzpy-0.2.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 3, 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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