JustSwitch
Utility & Location

Email OTP API

POST /api/v1/email-address-pincode/email-otp

The Email OTP from JustSwitch lets product teams otp email addresses in real time through a single REST integration. Designed for the Location / Email lane, it removes manual checks, reduces drop-offs in onboarding funnels, and returns structured JSON that your risk engine, CRM, or core banking system can consume instantly.

  • Real-time otp for email addresses with sub-300ms median latency
  • Production-grade REST JSON with sandbox & webhook support
  • UIDAI / NPCI / MCA aligned partner routing where applicable
  • Audit logs, idempotency keys & enterprise SLA on JustSwitch
Latency
< 300 ms
Uptime SLA
99.9%
Format
REST / JSON
Sandbox
Included

What is Email OTP?

The Email OTP from JustSwitch lets product teams otp email addresses in real time through a single REST integration. Designed for the Location / Email lane, it removes manual checks, reduces drop-offs in onboarding funnels, and returns structured JSON that your risk engine, CRM, or core banking system can consume instantly.

Every request is authenticated with API keys, logged for audit, and routed through regulated partner rails where required. Responses follow a consistent `{ ok, data, message }` envelope so you can ship once and reuse the same error-handling patterns across all JustSwitch endpoints.

OTP flows are built for consent-first UX: trigger delivery on your UI, verify the user-entered code, and persist only the tokens or statuses your compliance team approves — never raw Aadhaar data unless your licence permits.

Developers choose JustSwitch for Email OTP because we aggregate multiple upstream providers behind one contract, one wallet settlement, and one support desk — so you launch faster while your compliance team retains full audit visibility through dashboard logs and exportable reports.

Fintech Enterprises SaaS System integrators

Technical specification

Endpoint details for Email OTP integration on JustSwitch.

POST /api/v1/email-address-pincode/email-otp
Protocol HTTPS REST / JSON
Authentication Bearer API Key + IP allow-list
Sandbox Available — no live debits
Median latency < 300 ms
Rate limits Burst-friendly — contact for enterprise tiers
Webhooks Yes — signed callbacks
Idempotency reference_id recommended
API slug email-otp

Request parameters

reference_id string required

Your unique transaction or session reference for reconciliation

consent boolean required

User consent flag — required for regulated KYC / verification flows

otp string

6-digit OTP — required on verify step only

Response fields

status string

success | pending | failed

reference_id string

Echo of your request reference

verified_at datetime

ISO-8601 timestamp of completion

otp_sent boolean

Whether OTP dispatch succeeded

message string

Human-readable result or error detail

Key features

REST + JSON

Dedicated OTP send & verify endpoints with TTL and retry policies.

Sandbox mode

Test end-to-end without debiting wallet or hitting live rails.

Webhooks

Async callbacks for pending states — payments, recharge, KYC, payouts.

Dashboard logs

Searchable request history with filters for support & audits.

Low latency

Median sub-300 ms for verification-class endpoints in production.

Enterprise SLA

99.9% uptime target with redundant routing and monitoring.

Who uses Email OTP?

Fi

Fintech startups

Ship email addresses features in days, not quarters.

En

Enterprises

Replace legacy screen-scraping with compliant APIs.

Sa

SaaS platforms

Embed verification inside your vertical workflow.

Sy

System integrators

Standardise client deliveries on one aggregator.

How it works

  1. 01

    Call the send endpoint with user identifier & consent reference.

  2. 02

    User enters OTP in your app; you pass it to the verify endpoint.

  3. 03

    Store verification token/status; proceed with onboarding or transaction.

Sample integration

Illustrative JSON for Email OTP — see developer docs for live schemas.

POST Request
{
    "identifier": "9876543210",
    "consent": true,
    "reference_id": "REQ-2026-001"
}
200 Response
{
    "ok": true,
    "message": "Success",
    "data": {
        "status": "success",
        "reference_id": "JS-DPMCB0WX",
        "verified_at": "2026-06-23T22:50:09+00:00"
    }
}

Business benefits

  • Reduce manual ops cost by up to 70% on verification-heavy journeys
  • Improve conversion with inline validation instead of offline turnaround
  • Single contract & settlement across 200+ Indian fintech APIs
  • Configurable OTP TTL, resend limits & fraud throttling
  • Dedicated solutions engineering for enterprise rollouts

Frequently asked questions

What is Email OTP used for?

It automates Location / Email workflows so your application can verify or transact in real time without building direct integrations with multiple upstream providers.

How do I integrate Email OTP in my app?

Sign up on JustSwitch, obtain sandbox API keys, call the REST endpoint with JSON body, handle the unified response envelope, then switch to production keys after UAT sign-off.

How do I authenticate requests?

Use Bearer API keys from the JustSwitch dashboard. Sandbox and production keys are separated; rotate keys anytime without downtime.

Is there a sandbox for testing?

Yes — every API supports sandbox mode with simulated responses so engineering, QA, and compliance can sign off before go-live.

What about webhooks and async status?

Long-running operations (payments, recharge, some KYC steps) emit webhooks to your HTTPS endpoint with signed payloads for replay protection.

Is Email OTP compliant for regulated use in India?

JustSwitch routes requests through authorised AUA/KUA, NPCI, MCA and partner networks. Your legal team should map consent, data retention and licence obligations to your use case.

Start building with Email OTP

Sandbox keys in minutes. Production access with compliance review for regulated endpoints.