V1.2 REST API Authentication

V1.2 wraps the familiar V1 REST API with ~80% of V2's security features. Same 3-step flow, no iframe, built-in protection at the pipeline level.

Coming Soon

V1.2 is currently in development. This page describes the planned feature set. Subscribe to updates in your Akedly dashboard to be notified when V1.2 launches.

Why V1.2?

V1.0 gives you full API control but no built-in security. V2.0 handles everything but requires an iframe. V1.2 fills the gap: REST API simplicity with automatic security.

Feature	V1.0	V1.2	V2.0
Integration Style	REST API	REST API	Iframe Widget
UI Control	Full (you build it)	Full (you build it)	Managed by Akedly
Captcha Protection	Implement your own	Built-in via SDK/CDN	Built-in (widget)
Device Fingerprinting	Implement your own	Pipeline-level	Widget-level
Rate Limiting	Implement your own	Pipeline-level	Widget-level
Circuit Breaker	Implement your own	Pipeline-level	Widget-level
PPSA Pricing	No	No	Eligible
Telegram Support	No	No	Yes
Security Coverage	DIY	~80% of V2	Full

Key Innovation: Captcha Without an Iframe

V1.2's standout feature is captcha verification that works entirely through your existing REST API flow -- no iframe, no managed UI, no Akedly-controlled frontend.

Multiple integration options to fit your stack:

Name
Crafted SDKs
Type
JS, Python, PHP, Go
Description
Official SDKs that handle captcha challenge generation and verification behind the scenes. Drop-in integration with your existing backend code.
Name
Source CDNs
Type
script tag
Description
Lightweight script tags for frontend captcha rendering. Minimal footprint, no framework dependency. Works with any web application.
Name
Web Worker Runners
Type
browser
Description
Run captcha verification in a Web Worker for zero UI thread impact. No visible elements, no layout shifts, no user friction.
Name
Mobile App Kits
Type
iOS, Android
Description
Native SDKs for iOS and Android. Integrate captcha directly into your mobile app without WebViews.

Pipeline-Level Security

Unlike V2.0 where security is configured per-widget, V1.2 applies security at the pipeline level. This means all API calls through a pipeline automatically inherit its security settings.

What Gets Protected

Fingerprinting: Device identification applied to all transactions through the pipeline
Rate Limiting: Per-phone, per-device, and per-pipeline limits enforced server-side
Circuit Breaker: Automatic flood detection and suspension at the pipeline level
Captcha: Verified before OTP delivery via your chosen integration method (SDK, CDN, Worker, or Mobile Kit)

What Stays the Same

Same 3-step REST API flow as V1.0 (create, activate, verify)
Same endpoints, same request/response format
Full control over your UI and user experience
Pay-per-message billing model
All existing V1.0 features (custom OTP, email support, multi-channel delivery)

Who Should Use V1.2

V1.2 is ideal if you:

Currently use V1.0 and want built-in security without migrating to an iframe-based flow
Need full UI control but don't want to build your own captcha, fingerprinting, and rate limiting
Prefer REST APIs over embedded widgets
Want a smooth upgrade path from V1.0 (minimal code changes)

Stick with V2.0 if you:

Want PPSA pricing eligibility
Need Telegram channel support
Prefer a fully managed UI with zero frontend code
Want the maximum level of built-in security

Migration Path from V1.0

Upgrading from V1.0 to V1.2 will be straightforward:

Enable V1.2 security features on your pipeline in the dashboard
Add captcha integration using your preferred method (SDK, CDN, Worker, or Mobile Kit)
Test -- your existing create/activate/verify flow stays the same
Deploy -- pipeline-level security activates automatically

No endpoint changes. No response format changes. Your existing V1.0 integration code continues to work with security layered on top.

Stay Updated

Subscribe to Updates

Compare All Methods

Questions?

Reach out to the team at support@akedly.io or contact the co-founders directly at muhad@akedly.io or hana@akedly.io.