Install Python
Use uv.Publish Python
uv add ranglerpy works after the ranglerpy distribution exists on PyPI.
Reserve the package name on PyPI before the first release. Use a PyPI API token for manual releases, or trusted publishing from GitHub Actions once release automation is ready.
Run this from the package repo.
Current SDK
ranglerpy is first because Python is the shortest path for fintech backends, internal automation, research workflows, and compliance tooling.
It ships with these pieces.
- sync and async API clients
client.v1.*resources for the current public API- list responses with
data - dynamic response objects with dict and attribute access
- webhook signature verification
- webhook duplicate-delivery helpers
- event feed helpers for loading earlier events and checking missed deliveries
- portal API helpers for organizations, API keys, subscriptions, usage, and webhook endpoints
Auth Model
Rangler has two auth modes.- customer API resources use
api_key - portal management resources use
bearer_token
Webhooks
UseWebhook.construct_event as the recommended receiver entry point.
Webhook.construct_event verifies the signature and timestamp and parses the event. It does not durably accept the event for your application. In production, insert event.id and the payload into a shared, database-backed inbox before returning 2xx. The optional InMemoryIdempotencyStore is only for local examples and single-process tests.
Rangler webhook events use a consistent format with a resource inside data.object.
display is for humans. data.object is for code. If an enriched signal is attached, read it from event.data.signal.
Read earlier events
Useclient.v1.events to load earlier events or check for missed deliveries across the market, an issuer, or a fund.
Metadata
Rangler does not currently expose customer writable metadata on public API resources. When metadata is added, use it only for customer controlled key value data that helps your own system reconcile Rangler resources. Do not use future metadata for secrets, credentials, access decisions, or values that should be visible in the Rangler product. Example use cases.- store your internal company identifier on a watchlist entry
- store your internal workflow identifier on a webhook subscription
- store a reference ID that lets your job connect Rangler events to your own records