billos (Python)

BillOS from Python: legally valid Israeli tax documents (חשבונית מס, קבלה, זיכוי), the expense ledger, webhooks and the regulatory outputs, over one small client with no dependencies beyond the standard library (Python 3.9+).

pip install billos

from billos import BillOS, BillOSError

billos = BillOS(api_key=os.environ["BILLOS_API_KEY"])
bid = billos.businesses.list()["businesses"][0]["id"]

created = billos.documents.create(bid, {
    "docType": 320,
    "priceMode": "gross",
    "party": {"name": "דנה לוי", "phone": "0521111111"},
    "lines": [{"description": "איפור כלה", "quantity": 1, "unitPriceExVat": 120000}],
    "payments": [{"method": "card", "amount": 120000}],
}, idempotency_key="order-8812")

issued = billos.documents.issue(bid, created["document"]["id"])
print(issued["document"]["docNumber"])

pdf = billos.documents.print(bid, created["document"]["id"])   # Binary: .bytes, .content_type, .variant
link = billos.documents.share(bid, created["document"]["id"])   # a public URL for the customer

Money is integer agorot everywhere, exactly like the API (₪354.00 is 35400); a foreign-currency document ("currency": "USD") is in that currency's cents. Nothing in the client converts.

What you get

• Every operation in the spec as namespace.method (snake_case): businesses, parties, documents, recurring, legacy, expenses, exports, files, webhooks, events, keys, usage, requests, sandbox, and for Connect and shared access access, connections, apps. OPERATIONS (method and path per operation) is generated from the OpenAPI spec, and a test checks every operation has a method, so the client cannot lag behind the API.
• The conventions handled: X-Api-Key, the {ok, ...} envelope returned as a dict (plus request_id), Idempotency-Key from idempotency_key=, Retry-After honoured.
• api_version="2026-09-08" pins a dated API version (sent as BillOS-Version); the default is the current one.
• Retries on 429 / 502 / 503 / 504 and network errors, up to max_retries (default 2), for GET/DELETE and for POSTs carrying an idempotency key; never for a POST without one.
• BillOSError with status, reason, request_id, body, retryable. Branch on reason.
• Binary answers (documents.preview, documents.print, files.get, a PDF report) come back as Binary(bytes, content_type, variant, request_id).
• verify_webhook_signature(secret, header, raw_body) for the X-BillOS-Signature header.
• access_token="bkat_…" instead of api_key= acts for one business whose owner connected your app (Connect).
• A bk_test_ key answers from the sandbox with no change on your side (billos.sandbox.seed() fills it with demo data).

Documentation and the OpenAPI spec: https://docs.billos.co.il. MIT.

Connect: acting for someone else's business

An API key holds the businesses you opened. A Connect token holds one business whose owner connected your app (OAuth 2.0 with PKCE, guide: https://docs.billos.co.il/connect):

merchant = BillOS(access_token=token)                # bkat_…, one business, the granted scopes
merchant.documents.list(business_id)

dev = BillOS(api_key=key)                            # your key sees connected businesses too
dev.apps.create({"name": "My App", "redirectUris": ["https://app.example/cb"], "scopes": ["documents:read"]})
dev.connections.list(business_id)                    # what an owner connected, and the way out
dev.access.invite(business_id, {"email": "rina@example.com", "role": "accountant"})

What is new in 0.3.0

• Connect: access_token= for a per-business token, and the apps namespace to register and manage the app behind it (create, list, get, update, rotate_secret, delete).
• Shared access: access.list / access.invite / access.revoke open a business to a person by email and role (accountant, bookkeeper, viewer), and connections.list / connections.revoke are the owner's view of the apps connected to it.
• Fine scopes: a refusal names the half it needed (missing scope: documents:write). A key's coarse scope covers both halves, so nothing you hold changes.