Sendly Phone Verification for Openclaw

A high-performance phone verification skill that integrates the Sendly API to manage SMS-based OTP and 2FA authentication workflows.

sendly-live
v1.0.0
Apr 4, 2026
0
580
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install verifying-phones

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install verifying-phones using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Sendly Phone Verification?

This skill enables developers to implement robust phone verification systems using the Sendly Verify API. It streamlines the entire lifecycle of identity confirmation, from sending one-time passwords (OTP) to checking verification codes and managing session expiration. By utilizing Openclaw Skills such as this, engineering teams can quickly add secure verification layers to their applications without the overhead of building complex SMS infrastructure from scratch.

Whether you are verifying new user accounts or implementing multi-factor authentication, this skill provides a developer-friendly interface to Sendly's global delivery network. It supports international E.164 phone formatting and offers both direct REST API interactions and a dedicated Node.js SDK, ensuring seamless integration into modern backend or agentic workflows.

Sendly Phone Verification Use Cases

  • Verifying new user registrations to ensure authentic phone numbers.
  • Implementing two-factor authentication (2FA) for secure account access.
  • Creating passwordless login flows using SMS-delivered verification codes.
  • Preventing bot spam and fraud during signup by requiring mobile validation.
  • Integrating automated phone confirmation for e-commerce and logistics platforms.

How Sendly Phone Verification Works

  1. The application triggers a verification request by passing a target phone number in E.164 format to the Sendly endpoint.
  2. Sendly generates a unique OTP based on configured length and delivers it via SMS to the user's device.
  3. The skill returns a unique verification ID used to track the session status and its expiration timestamp.
  4. Once the user enters the code, the application calls the check endpoint to validate the input against the active session.
  5. The skill returns a final status such as verified, failed, or expired, allowing the application to proceed with the user's request.

Sendly Phone Verification Setup

To integrate this component into your Openclaw Skills setup, you must first obtain an API key from the Sendly dashboard.

Install the Node.js SDK via npm:

npm install @sendly/node

Configure your environment variables to store your credentials:

export SENDLY_API_KEY="your_sk_live_key_here"

Initialize the client in your application:

import Sendly from "@sendly/node";
const sendly = new Sendly(process.env.SENDLY_API_KEY);

Sendly Phone Verification Data Schema & Taxonomy

The skill processes and returns structured JSON data for every verification attempt. Key schema elements include:

Property Type Description
id String The unique identifier for the verification session (e.g., ver_abc123).
status String The current state: pending, verified, failed, expired, or max_attempts_exceeded.
phone String The target mobile number in E.164 format.
expires_at ISO8601 The exact date and time when the OTP session becomes invalid.
sandbox_code String Included only in test mode to allow for automated testing without real SMS delivery.

Sendly Phone Verification Advanced Features

  • Hosted Verification Sessions: Deploy a zero-code, pre-built UI hosted by Sendly for a faster time-to-market.
  • Sandbox Testing: Use test API keys and the sandbox_code field to simulate full verification flows in CI/CD environments.
  • Custom Expiry and Length: Configure OTP code length (4-10 digits) and session timeouts (default 300s) to meet specific security requirements.
  • Resend Logic: Built-in support for resending OTPs to existing verification sessions to improve user experience.
  • Secure Token Validation: Server-side validation for tokens returned from hosted sessions to prevent client-side tampering.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*