Get Started

Introduction

Cobinar Phone is an internet-native virtual phone identity platform. It replaces SMS-based OTP with carrier-free authentication that runs entirely over HTTPS — no PSTN, no telecom providers, no per-message fees.

What a virtual phone number actually is

Every account on the platform is issued a permanent identifier formatted like a phone number — for example +999 482 918 102 or +0 184 938 221. The +999 and +0 prefixes are deliberately outside any real country code range, so a virtual number can never be mistaken for a routable PSTN number. It behaves like a username: globally unique, permanently linked to one account, never connected to a SIM card or carrier.

Cobinar Phone cannot send or receive real SMS or calls. If your product needs to reach an actual mobile phone number, this isn't the right tool — it's specifically for authentication flows where the "phone number" is really just an internet-native user identity.

How the pieces fit together

  • Developer Console (console.phone.cobinar.com) — where you create projects, applications, and credentials, and inspect OTP activity, webhooks, and logs.
  • API (api.phone.cobinar.com) — a Cloudflare Worker your backend calls to send and verify OTPs, manage applications, and register webhooks.
  • Webhooks (delivered from hooks.phone.cobinar.com) — signed HTTP callbacks your server receives when OTP events happen.
  • API Sandbox (test.phone.cobinar.com) — a browser-based tool for exercising the real API without writing any code first. See Testing Your Integration.

The account model

A developer account can own multiple projects. Each project can contain multiple applications. Each application gets its own independent set of four credentials and its own webhook subscriptions — so a single Cobinar account can safely run several unrelated products or environments side by side.

LevelContainsFree plan limit
Developer accountProjects
ProjectApplications10 projects
ApplicationCredentials, webhooks, OTP requests5 applications

Where to go next

If you want to see it work before reading anything else, open the API Sandbox — it lets you send a real OTP from your browser using credentials from an application you've created. Otherwise, continue to the Quickstart for the full walkthrough.