regiondo

A Python client for the Regiondo Booking API.

Implements the request signing scheme used by the Regiondo PHP/JS sample clients (HMAC-SHA256 over timestamp + public_key + http_build_query(params)), plus typed namespaces for every endpoint in the v1 spec.

Install

pip install py-regiondo

The distribution is py-regiondo, the import name is regiondo:

from regiondo import RegiondoClient

From source:

pip install -e ".[dev]"

Usage

from regiondo import RegiondoClient

client = RegiondoClient(
    public_key="YOUR_PUBLIC_KEY",
    private_key="YOUR_PRIVATE_KEY",
    sandbox=True,                # talks to https://sandbox-api.regiondo.com/v1/
    accept_language="de-DE",
)

# Catalog
categories = client.categories.list()
product = client.products.get(12345)
products = client.products.list(limit=20, active_only="true")
slots = client.products.timeslots(product_id=12345)

# Checkout flow
hold = client.checkout.create_hold(
    item={"product_id": 12345, "variation_id": 1, "qty": 2},
    currency="EUR",
)
totals = client.checkout.totals(input_data={"items": [...]})
order = client.checkout.purchase(
    input_data={"items": [...], "customer": {...}, "payment": {...}},
    currency="EUR",
)

# Partner / supplier
sales = client.partner.sold_items_list(date_from="2026-01-01", date_to="2026-01-31")

# Validation
client.validate.submit(item={"ticket_code": "ABC-123"})

Namespaces

Calling an arbitrary endpoint

client.get("products/availabilities/42", date_from="2026-01-01")
client.post("checkout/cancel", params={"reference_ids": "1,2,3"})
client.put("checkout/hold", params={"reservation_code": "X", "reserve_minutes": 15})
client.delete("checkout/hold", reservation_code="X")

All four methods sign the request, send PHP-style http_build_query params, and return the parsed JSON body. JSON bodies passed via json=... are not included in the signature, matching the reference PHP implementation.

Errors

Non-2xx responses raise:

All of them carry .status_code, .payload (parsed JSON body), and .response (raw requests.Response).

Tests

pip install -e ".[dev]"
pytest

The signing tests pin output against PHP 7.2's http_build_query (captured live) so the wire format stays compatible with the upstream verifier.

Releasing

Releases are published to PyPI automatically by the publish workflow when a GitHub Release is created. Auth is via PyPI Trusted Publishing (OIDC) — no API token secrets in the repo.

One-time PyPI setup

1. Sign in at https://pypi.org/manage/account/publishing/.
2. Under Add a new pending publisher (works even before the project exists), fill in:
   • PyPI project name: py-regiondo
   • Owner: e-dway
   • Repository name: py-regiondo
   • Workflow filename: publish.yml
   • Environment name: pypi
3. Create a matching GitHub Environment named pypi under Settings → Environments (optionally add required reviewers as a manual approval gate). Repeat for testpypi if you want to dry-run there.

Cutting a release

# 1. Bump the version in pyproject.toml
$EDITOR pyproject.toml          # version = "X.Y.Z"

# 2. Commit, tag, push
git commit -am "release: X.Y.Z"
git tag vX.Y.Z
git push origin main vX.Y.Z

# 3. Create the GitHub Release for tag vX.Y.Z
gh release create vX.Y.Z --generate-notes

The workflow verifies that the tag (minus the v prefix) matches the version in pyproject.toml before building and uploading. Dry-run uploads to TestPyPI are available via the workflow's Run workflow button (choose testpypi).

Notes

• The sandbox URL is https://sandbox-api.regiondo.com/v1/; production is https://api.regiondo.com/v1/. There are also regional production hosts (e.g. api.regiondo.de); pass them via base_url=.
• Regiondo limits API usage to 50,000 requests / 24 h (2,083 / h, 157 / 5 min). Prefer webhooks where possible.
• /checkout/avaialableassignees is misspelled upstream; the wrapper client.checkout.available_assignees() uses the misspelled path on the wire.