🍍 PinappleClient 🍍
Python client for the Pinapple encryption API with automatic token management and robust error handling.
Installation
pip install PinappleClient
Quick Start
from pinapple_client import PinappleClient
client = PinappleClient(
user="username",
password="password",
api_url="https://api.pinapple.com"
)
# Encrypt/decrypt individual PINs
encrypted = client.encrypt_pins(["123456", "789012"])
decrypted = client.decrypt_pins(["enc_abc123", "enc_def456"])
# Validate PINs
validation = client.validate_pins(["123456", "789012"])
DataFrame Operations
Pandas
import pandas as pd
df = pd.DataFrame({
'id': [1, 2, 3],
'pin': ['123456', '789012', '345678']
})
# Encrypt
encrypted_df = client.encrypt_pandas_dataframe(df, 'pin', batch_size=100)
# Decrypt
decrypted_df = client.decrypt_pandas_dataframe(encrypted_df, 'pin', batch_size=100)
Polars
import polars as pl
df = pl.DataFrame({
'id': [1, 2, 3],
'pin': ['123456', '789012', '345678']
})
# Encrypt
encrypted_df = client.encrypt_polars_dataframe(df, 'pin', batch_size=100)
# Decrypt
decrypted_df = client.decrypt_polars_dataframe(encrypted_df, 'pin', batch_size=100)
Configuration
client = PinappleClient(
user="username",
password="password",
api_url="https://api.pinapple.com",
refresh_token_after_x_minutes=5, # Token refresh buffer (default: 5)
timeout=30, # Request timeout (default: 30)
max_retries=3, # Retry attempts (default: 3)
backoff_base=2.0 # Exponential backoff (default: 2.0)
)
Token Management
- Automatic token refresh before expiration
- Thread-safe token operations
- JWT payload parsing for expiration tracking
Network Resilience
- Exponential backoff retry:
backoff_base ^ (attempt + 1) - Handles 503 database errors
- Connection/timeout error recovery
License
GPL-3.0
Links
Metadata
Release files for PinappleClient 2.0.6
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 |
|---|---|---|---|---|
| pinappleclient-2.0.6.tar.gz | 9.7 kB | Without provenance | Details for pinappleclient-2.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pinappleclient-2.0.6-py3-none-any.whl | Python 3 | none | any | Details for pinappleclient-2.0.6-py3-none-any.whl |
Total release size: 18.1 kB
Release files / pinappleclient-2.0.6.tar.gz
| Download URL | pinappleclient-2.0.6.tar.gz |
|---|---|
| Size | 9.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8f9e0c05225e006eb6c8fe554945d80b2bbcdb38acab3d0b8c8ad434e75cce9
|
|
BLAKE2b-256 checksum How to use checksums |
46c413f7410ba254fe97cbc503989c2202f401c09e2b694c492adf408f39f005
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / pinappleclient-2.0.6-py3-none-any.whl
| Download URL | pinappleclient-2.0.6-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3c3b3f8dcb39dc0d1a8df4fe98bfd7ade2d375e461264c5d78641b16c472035b
|
|
BLAKE2b-256 checksum How to use checksums |
4fea182cdc05de076516cf4374e070fc3f97728c65568703357eefc79b78e834
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for PinappleClient 2.0.6
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.