Plug in via the API today. Native integrations next.
OpenSettle is in early access. The first-party surface — REST API, Node / Python / Go / Rust SDKs, signed webhooks, OpenAPI 3.0 spec — is what every integration sits on today. Native connectors for accounting, CRM, analytics, and on/off-ramp partners come once we’ve learned from production merchants which ones actually move the needle.
Conventional REST resource shape — payments, subscriptions, customers, webhook events — fully addressable, idempotency-keyed, cursor-paginated. OpenAPI 3.0 spec at /v1/openapi.json.
@opensettle/sdk (npm), opensettle (PyPI & crates.io), and the Go module. Each SDK tracks the v1 API one-to-one — types are kept in lockstep with the same shared schemas the API validates against.
HMAC-signed deliveries with idempotency keys, exponential retries, and a full delivery log. Handler examples in the docs work on Vercel, Cloudflare Workers, and any Node runtime.
Three-pane Scalar-rendered explorer at api.opensettle.io/v1/docs. Try every endpoint without writing a line of code.
Need a specific integration?
Tell us which tool, what flow, and how soon. Email partnerships@opensettle.io. If we’re hearing the same request from multiple merchants, it moves up the queue.