genieos — Python SDK
The official Python SDK for GenieOS. Sync and async clients, typed responses (Pydantic), automatic idempotency, retry-on-429/5xx with exponential back-off, and webhook signature verification.
Install
pip install genieos
Requires Python 3.9+ and httpx>=0.27, pydantic>=2.6.
Quickstart (sync)
API keys are minted in Settings → API keys. Production keys look like
gos_live_…; sandbox keys look like gos_test_…. Put the secret in
GENIEOS_API_KEY (never commit it).
from genieos import GenieOS
with GenieOS(api_key="gos_live_...") as gos:
ws = gos.workspace.get()
print(ws.name, "on", ws.plan)
send = gos.templates.send(
"welcome",
to="aki@example.com",
variables={"firstName": "Aki"},
)
print("queued:", send.id)
The API key is also picked up from the GENIEOS_API_KEY env var,
matching the Node SDK and CLI.
Quickstart (async)
import asyncio
from genieos import AsyncGenieOS
async def main():
async with AsyncGenieOS() as gos: # GENIEOS_API_KEY env var
await gos.events.emit(
"subscription.cancelled",
email="aki@example.com",
traits={"tier": "pro", "reason": "moving to weekly"},
)
asyncio.run(main())
Webhook verification (Flask)
import os
from flask import Flask, request, abort
from genieos import verify_webhook, WebhookSignatureError
app = Flask(__name__)
@app.post("/genieos/webhook")
def webhook():
try:
delivery = verify_webhook(
request.get_data(as_text=True),
request.headers,
secret=os.environ["GENIEOS_WEBHOOK_SECRET"],
)
except WebhookSignatureError as e:
abort(400, str(e))
if delivery.type == "send.delivered":
... # handle it
return "", 204
verify_webhook rejects out-of-window timestamps (default ±5 min) and
performs constant-time signature comparison. The same module exposes
sign_webhook for local testing.
Error handling
from genieos import (
GenieOSRateLimitError,
GenieOSValidationError,
GenieOSAuthError,
)
try:
gos.events.emit("checkout.completed", email="aki@example.com")
except GenieOSRateLimitError as e:
time.sleep(e.retry_after_seconds)
except GenieOSValidationError as e:
log.warning("422: %s", e.body)
except GenieOSAuthError:
rotate_my_key()
All SDK errors inherit from GenieOSError and expose .code,
.status, .request_id, .body.
License
MIT
Metadata
Release files for genieos 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| genieos-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for genieos-0.1.2-py3-none-any.whl |
Release files / genieos-0.1.2-py3-none-any.whl
| Download URL | genieos-0.1.2-py3-none-any.whl |
|---|---|
| Size | 29.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
32dd8c94c9be46b79826b3de38cbf7e073b4054f19284f4ed214475731bd55ab
|
|
BLAKE2b-256 checksum How to use checksums |
cc77a76adc283e6b2053847ec9db9a2788448f7209aebecb27d409e99d50f6ed
|
| 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 8, 2026.
Transparency logSecurity for genieos 0.1.2
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
1 file in this release has been uploaded with provenance metadata.
Attestation for genieos-0.1.2-py3-none-any.whl
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 8, 2026.
Transparency logA 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.