Skip to main content
The Authmatech REST API gives you programmatic access to silent mobile identity verification and the identity-intelligence suite — Verify, Trust, Shield, Detect, and Target — from one consistent HTTP interface. (Stuck, Stuck+, and Connect are dashboard features and have no developer endpoints.) Every request travels over HTTPS, carries a JSON body, and returns a JSON response wrapped in a standard envelope.

​
Base URL

Plain HTTP is not supported. All traffic must use HTTPS to protect your credentials and your customers’ data in transit.

​
Authentication

Every server-side request requires two headers:
The API key is a server-side secret. Browser and mobile SDK flows use a narrow-scoped X-SDK-TOKEN instead, which can only register sessions. See Authentication.

​
Request format

Requests with a body must set Content-Type: application/json and send valid JSON.

​
Response envelope

Every response — success or failure — uses the same shape:
Read your result from data. Treat success: false or a non‑200 status as an error and surface messages[].message. Full details in Errors & responses.

​
Phone number format

All mobile numbers use E.164 — a leading +, the country code (no leading zero), and the subscriber number, with no spaces, dashes, or parentheses.
Libraries such as Google’s libphonenumber (libphonenumber-js) convert local formats to E.164 before you send them.

​
Endpoint groups

Verify

Confirm a customer controls their mobile number, silently.

Identity intelligence

Trust score, Shield risk decisions, and Detect anomalies.

SDK & sessions

Register an SDK session from the native mobile SDK.

Target

Capture high-intent anonymous visitor opportunities.

Client portal

Usage, verification history, and API-key management.
Administrative endpoints under /v1/api/dashboard/** power the Authmatech dashboard and are not part of the standard developer integration surface.

​
Support

Questions or issues? Email connect@authmatech.com (Sun–Thu, 09:00–18:00 Amman time).