Skip to main content

paywise Python SDK

PyPI

Official Python client for the paywise Case Management API v2 and Partner API v2.

This SDK is generated with Fern from the published OpenAPI specs. Please open issues and pull requests in developer-resources, not against the generated code here.

Installation

pip install paywise

Requires Python 3.10 or newer.

Usage

import os
from paywise import Paywise, PaywiseEnvironment

client = Paywise(
    environment=PaywiseEnvironment.SANDBOX,  # or PaywiseEnvironment.PRODUCTION (default)
    token=os.environ["PAYWISE_API_KEY"],
)

health = client.case_management.health.check()

Both APIs share one client:

  • client.case_management.* — claims, orders, mandates, debtors, payments, statements, webhooks, …
  • client.partner.* — managed companies, company users, usage, webhooks, …

An async client with the same interface is available as AsyncPaywise.

Acting on behalf of a company (Partner keys)

Partner keys call the Case Management API for a managed company by sending X-On-Behalf-Of-Company. Set it once on the client:

company_client = Paywise(
    environment=PaywiseEnvironment.SANDBOX,
    token=os.environ["PAYWISE_PARTNER_API_KEY"],
    on_behalf_of_company="<company id>",
)

Direct Case Management keys must not send this header.

Pagination

List methods return a pager that iterates across all pages:

for claim in client.case_management.claims.list_claims(limit=50):
    print(claim.id)

Use .iter_pages() to work page by page.

Errors

Non-2xx responses raise a typed error per status code (for example paywise.case_management.UnauthorizedError), all subclasses of paywise.core.ApiError:

from paywise.core import ApiError

try:
    client.case_management.claims.list_claims()
except ApiError as err:
    print(err.status_code, err.body)

Retries and idempotency

Failed requests (408, 409, 429, 5xx) are retried twice by default (max_retries on the client or per request via request_options), honouring Retry-After. Write operations that accept an Idempotency-Key take it as a parameter, and retries reuse the same key.

Reference

The full list of methods is in reference.md.

License

MIT — see LICENSE.

Metadata

Release files for paywise 0.1.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 paywise 0.1.0
File Size Uploaded Provenance
paywise-0.1.0.tar.gz 331.1 kB With provenance Details

Built distribution (wheel)

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

Total release size: 982.4 kB

Release files / paywise-0.1.0.tar.gz

Download URL paywise-0.1.0.tar.gz
Size 331.1 kB
Tags Source
SHA-256 checksum
How to use checksums
9f9c71e29131822aa6b07ccc13513d0288ec05d789921597f10c36b2f2baab1a
BLAKE2b-256 checksum
How to use checksums
30e64a33966cfd736804acbc9c4f684cb75c004bc3bc2e06cf49fa9b8764945b
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 Oct 21, 2026.

Transparency log

Release files / paywise-0.1.0-py3-none-any.whl

Download URL paywise-0.1.0-py3-none-any.whl
Size 651.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
673fdb6b951d01081ddcdbb50d309b39de7155bd624b30746dbafb8567e23738
BLAKE2b-256 checksum
How to use checksums
ffbd72d88b1047e3d009630acb2ec82fa2674676ce12ef092de5033aa22659e9
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 Oct 21, 2026.

Transparency log

Security for paywise 0.1.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 paywise-0.1.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 21, 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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

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