AuthLink
One device. A trusted connection.

Every confirmation,
back to your phone.

Connect your website accounts to the original phone. Scan to bind, compare the codes, and approve in the app so your backend can verify the result.

Get AuthLink ↗ Start integrating →

Keep your existing accounts · React / Vue / JavaScript integration

Phone confirmation Scan to bind, confirm in the app
30 seconds Matching code refresh interval
120 seconds Request lifetime
One-time result Verified, consumed and persisted by your backend
A simple, complete flow

From a scan to a verified confirmation.

Browser, website backend and phone each play a clear role.
A clear confirmation flow that fits your existing application.

01 / CONNECT

Scan to bind the original device

Users sign in to your website, scan with AuthLink and check the website and account to complete binding.

02 / CONFIRM

Compare, then approve on the phone

The page and app show matching six-digit codes. Users check the website, account and code, then approve on their bound phone.

03 / VERIFY

Consume and verify on your backend

Your backend polls and consumes the one-time result, checks the user, purpose, state and expiry, persists the record, then updates the page.

Built around your account system

Your account system,
with original-device confirmation.

AuthLink handles device binding and phone approval. Your website keeps control of its users, sessions and permissions, and decides what a verified confirmation permits.

Explore the integration flow →
⌘
Isolated by website and account

Identical account IDs in different tenants have independent bindings. A phone can hold separate bindings for multiple websites.

↗
Fits your existing frontend

Use React or Vue components, or a JavaScript dialog, with multiple languages, three layouts and lifecycle cleanup.

✓
One-time results and idempotent recovery

Creation and consumption use stable idempotency keys to recover the same request when a network outcome is uncertain.

◉
Foreground inbox, optional notifications

View pending requests in the app and enable notifications for timely reminders.

Take the connection with you

Put AuthLink on your phone.

Bind and confirm on a real device.
Android 11+ / iOS 16+

ANDROID / DIRECT APK

Android

Download the standalone APK. Install updates over the existing app using a compatible signature to preserve bindings and device keys.

APK coming soon Download link not yet published
iOS / APP STORE · TESTFLIGHT

iPhone

Get the client through the App Store or TestFlight. This link becomes available when the official release is configured.

iOS coming soon For iPhone running iOS 16 or later

Get the app from official sources. Unpublished channels remain marked as coming soon.

Everything you need to integrate

From your first line of code to verified results.

APIs, fields, callbacks and SDK examples,
in one documentation hub.

01 / SERVER

Server integration

Tenant credentials, request creation, status checks, result consumption, Go / Node SDKs and parameter references.

Read server docs → 02 / CLIENT

Client integration

JavaScript, React and Vue examples, component options, events and usage guidance.

Read client docs →
Before you connect

A few things to know.

Do I need to replace my existing sign-in system?

Keep your existing sign-in system. AuthLink binds to a stable user ID from your website; your backend manages confirmation records.

Is this a regular Authenticator code?

Use the AuthLink app to check and approve the request on your bound phone. The displayed code alone cannot complete confirmation.

Can I bind again after changing phones or deleting a binding?

Binding cannot currently be restored on a replacement phone. Keep your bound phone safe; deleting a binding permanently prevents this website account from binding again.

Are server webhooks available?

Your website backend polls and consumes the result, then notifies the page or SDK. There is no server webhook; frontend success events only update the UI.