PIE Playground: Test OTP Delivery Before You Integrate
Use your free credits to send an OTP to your phone, inspect the selected route and verify the code. Test from your dashboard before adding the API to your app.
Send and Verify a Code From Your Dashboard
Use the PIE Playground to test OTP delivery with the channels and templates configured on your account.
Enter your phone number and request a code. The route inspector shows the selected channel and any fallback attempts. Enter the code you receive to check verification.
The playground uses SecondFactor’s delivery and verification service, so you can check your setup before writing the integration.
- Attempt 1WhatsApp — no confirmation
- +8.0sFallback triggered automatically
- Attempt 2SMS — delivered
- Verify200 OK · code matched
Illustrative route. Yours depends on the channels enabled on your account and what your number can receive.
Test Delivery With Your Account Setup
Playground requests use real channels and account credits. Results depend on your channel setup, destination and recipient.
Real Delivery
Request an OTP over an eligible channel and check the message on your phone.
Route Inspection
See which channel was selected and whether delivery moved to another channel.
Code Verification
Enter the received code to confirm that verification succeeds.
Free Credits to Start
New accounts receive free credits to cover test sends.
How to Test an OTP
Test from the dashboard once your channel and template setup is complete.
Create an Account
Sign up for free credits, then complete the required channel and template setup.
Enter Your Number
Open the PIE Playground and send an OTP to a phone number you own.
Inspect the Route
Review the channel that was tried and any fallback in the route inspector.
Verify the Code
Enter the code from your phone to confirm the verification succeeds.
From the Playground to Your App
Call /Verifications to send a code, then /VerificationCheck with the returned SID and the code your user entered.
A check can return 200 for either a correct or incorrect code. Confirm that status is approved before granting access. Keep your API key on your server.
# 1. Send a code
curl -X POST "https://api.secondfactor.ai/v2/Services/$SERVICE_SID/Verifications" \
-H "X-API-Key: $SF_API_KEY" \
--data-urlencode "To=+9779841000000"
# 2. Use the SID returned by step 1
curl -X POST "https://api.secondfactor.ai/v2/Services/$SERVICE_SID/VerificationCheck" \
-H "X-API-Key: $SF_API_KEY" \
-d "VerificationSid=$VERIFICATION_SID" \
-d "Code=482915"
What to Look For While Testing
Check the selected channel, message content and verification result. Use numbers you control in the markets you plan to serve.
Which Channel Delivers
See which of your enabled channels the routing engine picks for your number.
Fallback Attempts
If delivery isn’t confirmed within eight seconds, inspect the next attempt. Another eligible channel must be available for fallback.
How the Message Reads
Check the message as it arrives on your phone, using your template.
Whether Verification Passes
Confirm that the code you received is accepted.
More SecondFactor Features
Automatic OTP Routing and Fallback
Route codes through eligible channels, with fallback after eight seconds without delivery confirmation. Learn more →
OTP Delivery Logs and Costs
See the channel, delivery status and cost of every OTP request. Learn more →
OTP Template Management
Create templates per channel, track approval and choose one per request. Learn more →
Frequently Asked Questions
Write to support@secondfactor.ai for anything not covered here.
Does the Playground Send Real OTPs?+
Yes. Playground requests use real delivery channels and account credits. Test with a phone number you own.
What Does PIE Stand For?+
Price Intelligence Engine, the routing engine that selects the lowest-cost eligible channel for each OTP.
Do I Need to Write Code to Use the Playground?+
No. Send and verify codes directly in your dashboard. Complete your channel and template setup first, then use the API when you are ready to integrate.
Are Test Sends Rate-Limited?+
Yes. Per-number burst and hourly limits apply. Requests over those limits are rejected and are not charged. See the send reference for rate-limit responses.
What Happens When My Free Credits Run Out?+
Top up your balance on the Billing & credits page of the dashboard to keep sending.
Which Channels Can I Test?+
Test channels enabled on your account with the required sender and template approvals. The recipient must support the channel; fallback requires at least two eligible channels.
Send Your First Test OTP
Create an account to open the PIE Playground with free credits, or talk to our team about channels and pricing for your destination markets.