Built for developers
Add consent, identity, and data rights to your application with a few lines of code.
import { Overturo } from "@overturo/js"
const overturo = new Overturo({ publishableKey: "pk_live_..." })
// Embed a consent flow โ outcome arrives via onComplete
await overturo.consent.open({
flowId: "flw_...",
container: "#consent",
onComplete: (result) => console.log(result.consentToken)
})
JavaScript SDK
@overturo/js
TypeScript-first. Zero runtime dependencies. Embed, popup or redirect delivery โ or the Overturo field and the capture snippet in your own form.
Ruby SDK
overturo
Server-side gem for Rails, Sinatra, and any Ruby application โ typed resource clients, structured errors, and webhook signature verification.
REST API
/api/v1
JSON API with five authentication methods covering every integration role: backend servers, browser SDKs, user-authorized apps, AI agents, and human delegates. Consent records your server captured land through the Record API.
Forms
<overturo-consent-field>
Keep the form you have. The Overturo field, the capture snippet, a form platform's signed webhook or the Record API โ one receipt, four ways in.
AI Agent Authorization · OAP v1.0
Authorize AI agents with verifiable receipts
The Overturo Authorization Protocol (OAP) gives AI agents signed runtime receipts your counterparties can verify offline โ and every delegated authority freezes a durable authorization receipt behind them. Two adoption modes — Conductor (the platform decides) and Oversight (your policy engine decides, the platform witnesses). Apache-licensed SDKs for TypeScript and Python, a Go sidecar for Open Policy Agent, and a drop-in receipt-verification middleware for MCP servers.
All SDKs are open source under Apache-2.0 โ github.com/overturo.
Explore AI Agent Authorization →Consent & Notice Receipts
Receipts anyone can verify โ no platform access required
Every completed consent or notice decision issues a receipt aligned with ISO/IEC TS 27560:2023. Download it as the standard document, a standards-vocabulary export, or a signed receipt that verifies offline against published keys. The receipt schema is published at its own URL, and the full verification procedure lives in the developer docs. One canonical record schema, three kinds — consent records, notice records, and authorization records for delegated agent authority — each independently verifiable, served from its own endpoint.
Real-time webhooks
Get notified instantly when consent is granted, revoked, or expires. Subscribe to the events you care about โ every payload is cryptographically signed, so you can verify it came from us.
Event families
- Consent lifecycle โ granted, declined, expired
- Approvals โ granted, denied, expired, countered
- Signing โ signed, declined, expired, countered
What you need at each integration level
Share a link
You need: an account and a published flow.
Embed โ or keep your form
You need: an application and its publishable key; your application credential to commit a capture.
Build with API
You need: an application and an API token.
Seven APIs, one platform
Connect, Consent, Verify, Protect, Agree, Delegate, Comply โ each surface is a standalone API that handles one aspect of the personal data lifecycle.
Start building
Create a free account to access the API, SDKs, and developer docs.