paddle-billing-client
Paddle Classic vs Paddle Billing
- Paddle Classic is the original Paddle API, which is still in use by many merchants. More info can be found here
- If you are looking for the Paddle Classic API wrapper, please see
paddle-client
- If you are looking for the Paddle Classic API wrapper, please see
- Paddle Billing is the new API, which is just launched at 2023, August. Paddle Billing is a complete rewrite of the Paddle Classic API, and is designed to be more flexible and easier to use. More info can be found here
Django Integration
- For Paddle Classic, there is a Django integration available at
dj-paddleanddjango-paddle - For Paddle Billing, there is a Work In Progress Django integration available at
django-paddle-billing
📦 Features
- Pydantic models for all API requests and responses
- Tests with
pytestandVCR.pyfor mocking HTTP requests Website stalkerGithub Action to monitor any API changes- Pagination support with generator to process pages one by one
- Helper function for signature validation for webhooks
Tests
- Products
- Prices
- Discounts
- Customers
- Customer Credit balances
- Addresses
- Businesses
- Transactions
- Subscriptions (except activate)
- Subscription Resume
- Subscription Activate Trialing
- Adjustments
- Pricing Previews
- Reports
- Event types
- Events
- Notification Settings
- Notifications
- Notification logs
Installation
pip install -U paddle-billing-client
or install with Poetry
poetry add paddle-billing-client
Usage
from paddle_billing_client.client import PaddleApiClient
from apiclient.authentication_methods import HeaderAuthentication
client = PaddleApiClient(
base_url="https://sandbox-api.paddle.com",
authentication_method=HeaderAuthentication(token="your-paddle-token")
)
# Create a product
product = client.create_product(
ProductRequest(
name="Test Product New",
tax_category="standard",
description="Test Product Description",
image_url="https://example.com/image.png",
custom_data=dict(foo="bar"),
)
)
# Get all products
products = client.list_products()
# Get all prices
plans = client.list_prices()
# Pagination
from paddle_billing_client.pagination import paginate
from paddle_billing_client.models.notification import NotificationQueryParams
for notification in paginate(client.list_notifications, query_params=NotificationQueryParams(
status="delivered",
after='ntf_01hb1n6nw8yx1wwts2cyh632s9',
per_page=10
)):
# Process notifications page by page
print("Notification:")
print(len(notification.data))
print(notification.data[-1].id)
Debugging
To print the raw exception response, you can use the VerboseErrorHandler:
from paddle_billing_client.client import PaddleApiClient
from apiclient.authentication_methods import HeaderAuthentication
from paddle_billing_client.errors import VerboseErrorHandler
client = PaddleApiClient(
base_url="https://sandbox-api.paddle.com",
authentication_method=HeaderAuthentication(token="your-paddle-token"),
error_handler=VerboseErrorHandler
)
- Sandbox API url:
https://sandbox-api.paddle.com/ - Live API url:
https://api.paddle.com/
More usage examples can be found in tests.
Helper functions
from paddle_billing_client.helpers import validate_webhook_signature
# Validate webhook signature
is_valid = validate_webhook_signature(
signature_header=request.headers.get("HTTP_PADDLE_SIGNATURE"),
raw_body=request.data,
secret_key="your-paddle-secret-key",
)
Makefile usage
Makefile contains a lot of functions for faster development.
1. Download and remove Poetry
To download and install Poetry run:
make poetry-download
To uninstall
make poetry-remove
2. Install all dependencies and pre-commit hooks
Install requirements:
make install
Pre-commit hooks coulb be installed after git init via
make pre-commit-install
3. Codestyle
Automatic formatting uses pyupgrade, isort and black.
make codestyle
# or use synonym
make formatting
Codestyle checks only, without rewriting files:
make check-codestyle
Note:
check-codestyleusesisort,blackanddarglintlibrary
Update all dev libraries to the latest version using one comand
make update-dev-deps
4. Code security
make check-safety
This command launches Poetry integrity checks as well as identifies security issues with Safety and Bandit.
make check-safety
5. Type checks
Run mypy static type checker
make mypy
6. Tests with coverage badges
Run pytest
make test
7. All linters
Of course there is a command to rule run all linters in one:
make lint
the same as:
make test && make check-codestyle && make mypy && make check-safety
8. Docker
make docker-build
which is equivalent to:
make docker-build VERSION=latest
Remove docker image with
make docker-remove
More information about docker.
9. Cleanup
Delete pycache files
make pycache-remove
Remove package build
make build-remove
Delete .DS_STORE files
make dsstore-remove
Remove .mypycache
make mypycache-remove
Or to remove all above run:
make cleanup
📈 Releases
You can see the list of available releases on the GitHub Releases page.
We follow Semantic Versions specification.
We use Release Drafter. As pull requests are merged, a draft release is kept up-to-date listing the changes, ready to publish when you’re ready. With the categories option, you can categorize pull requests in release notes using labels.
List of labels and corresponding titles
| Label | Title in Releases |
|---|---|
enhancement, feature |
🚀 Features |
bug, refactoring, bugfix, fix |
🔧 Fixes & Refactoring |
build, ci, testing |
📦 Build System & CI/CD |
breaking |
💥 Breaking Changes |
documentation |
📝 Documentation |
dependencies |
⬆️ Dependencies updates |
You can update it in release-drafter.yml.
GitHub creates the bug, enhancement, and documentation labels for you. Dependabot creates the dependencies label. Create the remaining labels on the Issues tab of your GitHub repository, when you need them.
Building and releasing your package
Building a new version of the application contains steps:
- Bump the version of your package
poetry version <version>. You can pass the new version explicitly, or a rule such asmajor,minor, orpatch. For more details, refer to the Semantic Versions standard. - Make a commit to
GitHub. - Create a
GitHub release. - And... publish 🙂
poetry publish --build
🚀 Package Template Features
Development features
- Supports for
Python 3.10and higher. Poetryas the dependencies manager. See configuration inpyproject.tomlandsetup.cfg.- Automatic codestyle with
black,isortandpyupgrade. - Ready-to-use
pre-commithooks with code-formatting. - Type checks with
mypy; docstring checks withdarglint; security checks withsafetyandbandit - Testing with
pytest. - Ready-to-use
.editorconfig,.dockerignore, and.gitignore. You don't have to worry about those things.
Deployment features
GitHubintegration: issue and pr templates.Github Actionswith predefined build workflow as the default CI/CD.- Everything is already set up for security checks, codestyle checks, code formatting, testing, linting, docker builds, etc with
Makefile. More details in makefile-usage. - Dockerfile for your package.
- Always up-to-date dependencies with
@dependabot. You will only enable it. - Automatic drafts of new releases with
Release Drafter. You may see the list of labels inrelease-drafter.yml. Works perfectly with Semantic Versions specification.
Open source community features
- Ready-to-use Pull Requests templates and several Issue templates.
- Files such as:
LICENSE,CONTRIBUTING.md,CODE_OF_CONDUCT.md, andSECURITY.mdare generated automatically. Stale botthat closes abandoned issues after a period of inactivity. (You will only need to setup free plan). Configuration is here.- Semantic Versions specification with
Release Drafter.
🛡 License
This project is licensed under the terms of the MIT license. See LICENSE for more details.
📃 Citation
@misc{paddle-billing-client,
author = {Benjamin Gervan},
title = {Python wrapper around the new Paddle Billing API},
year = {2023},
publisher = {GitHub},
journal = {GitHub repository},
howpublished = {\url{https://github.com/websideproject/paddle-billing-client}}
}
Credits 
This project was generated with python-package-template
Metadata
Release files for paddle-billing-client 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 |
|---|---|---|---|---|
| paddle_billing_client-0.3.0.tar.gz | 22.9 kB | Without provenance | Details for paddle_billing_client-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| paddle_billing_client-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for paddle_billing_client-0.3.0-py3-none-any.whl |
Total release size: 52.1 kB
Release files / paddle_billing_client-0.3.0.tar.gz
| Download URL | paddle_billing_client-0.3.0.tar.gz |
|---|---|
| Size | 22.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
779ad33babb30bbbc2282b59a940b60511c7531b3bb6f6e0ddef04622ce0a2ca
|
|
BLAKE2b-256 checksum How to use checksums |
c196085504d191f4b7652ed87f07fd9f7219bd31e2bb9c1bae60a400fecb53cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.11.0 Linux/6.11.0-1018-azure
|
Release files / paddle_billing_client-0.3.0-py3-none-any.whl
| Download URL | paddle_billing_client-0.3.0-py3-none-any.whl |
|---|---|
| Size | 29.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
126c64e5299fbab31a09f2f61577ed949f86e8d10b4cba661ef1aced31025fba
|
|
BLAKE2b-256 checksum How to use checksums |
f91c32750582c7064cc5f2027e1a15d3aa92b765a246dcaba226cce99f5e75e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.11.0 Linux/6.11.0-1018-azure
|
Security for paddle-billing-client 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.
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.