Skip to main content
Authmatech is a mobile identity platform. It starts from one reliable fact — that a customer genuinely controls the mobile number they present — and turns that into a stream of products you can drop into the decisions your business already makes. Everything is exposed through a single REST API at https://service.authmatech.com, authenticated with the X-API-KEY and X-CLIENT-ID headers.

​
The building blocks

Verify

Silently confirm that a customer controls their mobile number — the no-OTP replacement for SMS one-time passcodes.

Trust

Turn an identity’s verification history into a single 0–100 trust score with a recommendation.

Shield

Evaluate the live session in real time and return a clear decision: ALLOW, CHALLENGE, REVIEW, or BLOCK.

Detect

Surface coordinated abuse across many events — retry bursts, multi-account-per-device usage, IP concentration, failure spikes.

Stuck+

Identify and reconnect with customers who became stuck during registration or verification.

Connect

Synchronize identity events and verification activity into your CRM and business systems.

​
How the products relate

The products are layered. Verify establishes identity; the intelligence products turn that identity — and the signals around it — into decisions; the recovery and sync products close the loop.
  1. Establish identity. Verify (and the Web SDK for browser flows) confirms control of the mobile number over the network. This is the foundation everything else builds on.
  2. Decide with intelligence. Trust scores an identity’s history, Shield decides on the live session, and Detect flags abuse patterns across many events. They share one request model, so you collect context once. See Identity intelligence.
  3. Recover and operationalize. Stuck+ recovers journeys that stalled; Connect pushes identity insight into the tools your teams already use; Target re-engages high-intent anonymous visitors.

​
A consistent API surface

Every product follows the same conventions, so once you integrate one, the rest are familiar:
  • Base URL — https://service.authmatech.com
  • Auth — X-API-KEY + X-CLIENT-ID headers on every server request
  • Format — JSON request and response bodies
  • Response envelope — a consistent { success, messages, data } shape, described in Errors & responses
  • Sessions — the sdkSessionId from the SDK links a verification to its device context, so Shield and Detect can reason about it

​
Where to go next

How silent verification works

The mechanics behind a no-OTP confirmation.

Identity intelligence

How Trust, Shield, and Detect score and decide.

The product suite

Each product mapped to its API endpoints.

Quickstart

Make your first call.