FraudLabs Pro SMS Verification

Name: FraudLabs Pro SMS Verification API
Brand: FraudLabs Pro SMS Verification
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationapiKey2 EndpointsREST

For Agents

Send a one-time SMS verification code to a customer's phone and confirm the code they enter. Authentication is the FraudLabs Pro license key on each request.

Connect the FraudLabs Pro SMS Verification to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FraudLabs Pro SMS Verification, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with FraudLabs Pro SMS Verification API.

Send a one-time SMS verification code to a customer phone number via /v1/verification/send

Customise the SMS body with a merchant-specific message

Confirm a user-entered OTP via /v1/verification/result

Use OTP success as a step-up signal that softens a borderline fraud verdict

GET STARTED

Start building with FraudLabs Pro SMS Verification API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for FraudLabs Pro SMS Verification, keeping it validated and agent-ready.

FraudLabs Pro SMS Verification is the standalone OTP module used as a step-up authentication signal in fraud workflows. The spec exposes two endpoints: /v1/verification/send delivers an SMS containing a one-time code with an optional custom message, and /v1/verification/result confirms whether a user-supplied code matches the one that was sent. It is typically wired into checkout or login flows to harden borderline transactions.

Use Cases

Patterns agents use FraudLabs Pro SMS Verification API for, with concrete tasks.

★ Checkout Step-Up Verification

When the merchant's fraud score for a checkout lands in the review band, /v1/verification/send pushes an OTP to the customer's phone. A successful match through /v1/verification/result tells the merchant the buyer at least controls the phone on file, softening the risk and letting the order proceed without manual review.

POST /v1/verification/send with the customer phone, then on user input POST /v1/verification/result with the otp and proceed if state=APPROVED

A customer signing in from a new device receives an SMS OTP through FraudLabs Pro before being granted a session. The merchant calls /v1/verification/send when the device fingerprint is unknown and only issues a session cookie after /v1/verification/result confirms the code, reducing account-takeover risk.

Trigger POST /v1/verification/send with the user's phone, prompt for the OTP, and verify with POST /v1/verification/result before establishing the session

Phone Possession for High-Value Actions

Before settling a high-value transfer or applying a coupon worth more than a configured threshold, the merchant requires an SMS-confirmed phone. The two-call FraudLabs Pro flow runs inline, completes within seconds, and produces an audit trail tying the action to a verified phone.

POST /v1/verification/send before the high-value action, then on user input POST /v1/verification/result and persist the outcome to the audit log

AI Agent Step-Up Flow

An agent handling a borderline order through Jentic calls FraudLabs Pro to send an OTP, asks the user for the code via the chat surface, and confirms it before approving the order. The license key is held in Jentic's vault and the agent only deals with structured success or failure responses.

Search Jentic for 'send an SMS verification code', execute /v1/verification/send, prompt the user, then execute /v1/verification/result and branch on the outcome

Key Endpoints

2 endpoints — fraudlabs pro sms verification is the standalone otp module used as a step-up authentication signal in fraud workflows.

METHOD

PATH

DESCRIPTION

POST

/v1/verification/send

Send an SMS with a one-time verification code

POST

/v1/verification/result

Confirm a user-entered verification code

POST

/v1/verification/send

Send an SMS with a one-time verification code

POST

/v1/verification/result

Confirm a user-entered verification code

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The FraudLabs Pro license key is stored encrypted in the Jentic vault. Agents receive a scoped execution token instead of the raw key, so prompt injection cannot leak the credential or trigger unauthorised SMS sends.

Intent-based discovery

Agents call Jentic search with intents like 'send an SMS verification code' or 'verify the OTP the user typed' and Jentic returns the matching FraudLabs operation with its input schema.

Time to first call

Direct integration: about half a day to wire send and verify into the application flow. Through Jentic: under 15 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio Verify

Twilio Verify supports SMS, voice, email, and TOTP codes with global delivery

Choose Twilio Verify for multi-channel verification at scale; choose FraudLabs SMS Verification when SMS is enough and the workflow already uses FraudLabs Pro for screening.

Complementary

FraudLabs Pro v2

FraudLabs Pro v2 provides order screening that pairs naturally with SMS step-up

Use FraudLabs Pro v2 to score the order, then this SMS verification API to step up borderline cases.

Alternative

MessageBird SMS

MessageBird SMS is a general-purpose SMS gateway suitable for OTP delivery

Choose MessageBird when you need SMS for many use cases beyond verification; choose FraudLabs SMS Verification for a turnkey OTP flow with built-in code management.

FAQs

Specific to using FraudLabs Pro SMS Verification API through Jentic.

What authentication does the FraudLabs SMS Verification API use?

Both endpoints take the FraudLabs Pro license key on every request. Through Jentic, the key is stored encrypted in the vault and substituted at execution time, so it never appears in the agent's prompt or transcript.

Can I send a custom-branded SMS message with this API?

Yes. The /v1/verification/send endpoint accepts a custom message field that is delivered alongside the OTP, so merchants can include their brand name and a short instruction for the recipient. The OTP itself is generated and tracked by FraudLabs Pro.

What are the rate limits for the FraudLabs SMS Verification API?

FraudLabs Pro charges per SMS sent and applies plan-level monthly quotas rather than per-second rate limits. International destinations may be billed at higher per-message rates than domestic ones.

How do I run an OTP step-up flow through Jentic?

Search Jentic for 'send an SMS verification code', execute /v1/verification/send with the customer phone, prompt the customer for the code, then execute /v1/verification/result with the same phone and the entered OTP. Approve the action if the result is APPROVED.

Is the FraudLabs SMS Verification API free?

There is no free tier for SMS sending — every successful /v1/verification/send call consumes credit at the destination's per-message rate. The /v1/verification/result confirmation call is free.

How do I confirm whether the user typed the correct code?

POST /v1/verification/result with the same phone number used for /v1/verification/send and the otp that the user entered. The response state is APPROVED if the code matches and has not expired, and DECLINED otherwise.