Skip to main content

Leal Python Library

fern shield pypi

Digital loyalty stamp cards in Apple Wallet and Google Wallet, for local businesses. This library covers the whole Leal API, so you can enrol customers, add stamps, redeem rewards and read a card's wallet links from your own application.

Table of Contents

Documentation

API reference documentation is available here.

Installation

pip install leal-sdk

Reference

A full reference for this library is available here.

Usage

Instantiate and use the client with the following:

from leal import Leal

client = Leal(
    token="<token>",
)

client.customer_cards.stamp(
    account_id=1,
    customer_id=1,
    id=1,
    stamps=1,
)

Environments

This SDK allows you to configure different environments for API requests.

from leal import Leal
from leal.environment import LealEnvironment

client = Leal(
    environment=LealEnvironment.PRODUCTION,
)

Async Client

The SDK also exports an async client so that you can make non-blocking calls to our API. Note that if you are constructing an Async httpx client class to pass into this client, use httpx.AsyncClient() instead of httpx.Client() (e.g. for the httpx_client parameter of this client).

import asyncio

from leal import AsyncLeal

client = AsyncLeal(
    token="<token>",
)


async def main() -> None:
    await client.customer_cards.stamp(
        account_id=1,
        customer_id=1,
        id=1,
        stamps=1,
    )


asyncio.run(main())

Exception Handling

When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error will be thrown.

from leal.core.api_error import ApiError

try:
    client.customer_cards.stamp(...)
except ApiError as e:
    print(e.status_code)
    print(e.body)

Advanced

Access Raw Response Data

The SDK provides access to raw response data, including headers, through the .with_raw_response property. The .with_raw_response property returns a "raw" client that can be used to access the .headers and .data attributes.

from leal import Leal

client = Leal(...)
response = client.customer_cards.with_raw_response.stamp(...)
print(response.headers)  # access the response headers
print(response.status_code)  # access the response status code
print(response.data)  # access the underlying object

Retries

The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).

Which status codes are retried depends on the retryStatusCodes generator configuration:

legacy (current default): retries on

  • 408 (Timeout)
  • 409 (Conflict)
  • 429 (Too Many Requests)
  • 5XX (All server errors, including 500)

recommended: retries on

  • 408 (Timeout)
  • 409 (Conflict)
  • 429 (Too Many Requests)
  • 502 (Bad Gateway)
  • 503 (Service Unavailable)
  • 504 (Gateway Timeout)

Use the max_retries request option to configure this behavior.

client.customer_cards.stamp(..., request_options={
    "max_retries": 1
})

Timeouts

The SDK defaults to a 60 second timeout. You can configure this with a timeout option at the client or request level.

from leal import Leal

client = Leal(..., timeout=20.0)

# Override timeout for a specific method
client.customer_cards.stamp(..., request_options={
    "timeout": 1
})

Custom Client

You can override the httpx client to customize it for your use-case. Some common use-cases include support for proxies and transports.

import httpx
from leal import Leal

client = Leal(
    ...,
    httpx_client=httpx.Client(
        proxy="http://my.test.proxy.example.com",
        transport=httpx.HTTPTransport(local_address="0.0.0.0"),
    ),
)

Contributing

While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!

On the other hand, contributions to the README are always very welcome!

Release files for leal-sdk 0.0.14

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for leal-sdk 0.0.14
File Size Uploaded
leal_sdk-0.0.14.tar.gz 71.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for leal-sdk 0.0.14
File Interpreter ABI Platform
leal_sdk-0.0.14-py3-none-any.whl Python 3 none any Details

Total release size: 197.8 kB

Release files / leal_sdk-0.0.14.tar.gz

Download URL leal_sdk-0.0.14.tar.gz
Size 71.0 kB
Tags Source
SHA-256 checksum
How to use checksums
452f5e0e623f96f108f26425bf5599859447ab4d12306c7d69ba30505603dc70
BLAKE2b-256 checksum
How to use checksums
b48ad7018915c92a9efa6513625950efee87fbc12691694da4a37f5f42b3791b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 29, 2026.

Transparency log

Release files / leal_sdk-0.0.14-py3-none-any.whl

Download URL leal_sdk-0.0.14-py3-none-any.whl
Size 126.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7bc517c97aa0b5732e76fce2c23fc1f69ae7c4c7960280fb957f14887641ea1d
BLAKE2b-256 checksum
How to use checksums
814fd0afdb3a808cc63b80fd44d97f3a16ee7621a6d72e9eaf9324c818fcc3d7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 29, 2026.

Transparency log

Release history Release notifications | RSS feed

0.0.15

2 release files

This release

0.0.14 This release

2 release files

0.0.13

2 release files

0.0.12

2 release files

0.0.11

2 release files

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