Sign in with REAL AUTH
OpenID Connect with PKCE, strict redirect matching, JWKS, and short-lived signed tokens. If you have integrated an OIDC provider before, this will be familiar.
Çözümler
For developers
OAuth 2.1 and OpenID Connect, a versioned REST API, signed webhooks, and a sandbox that behaves like production.
What you work with
Standards, not a bespoke protocol
Intents as a first-class API
Create a login intent or an action intent, bind it to exact values, poll or receive a webhook. Approval is cryptographically tied to what was displayed.
A sandbox that is genuinely separate
Sandbox and production credentials are distinct records with a hard environment discriminator. A test key cannot authenticate a production request, by construction.
Webhooks that resist replay
Signed with a timestamp and an event id, with delivery history and retries you can inspect rather than guess at.
Honest limits
Worth being clear about
Passkeys require a secure context, so your integration needs HTTPS in every environment where you test them beyond localhost. Parts of the platform are still being built, and anything not yet live is labelled as such in the developer area rather than documented as if it worked.
Read the developer documentation
Quickstart, API reference, webhook signatures and the OpenAPI description.