How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Messente Number Verification API

PIN-based phone number verification (2FA / one-time passwords).

Messente Number Verification API is one of 11 APIs that Messente publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Number Verification. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2.1.0.

Requests are made against a single base URL, https://api.messente.com/v1.

2 operations 2 paths 6 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.1.0
Base URL
https://api.messente.com/v1
Authentication
HTTP Basic
License
Resource Areas
1

Authentication & Security 1

Messente Number Verification API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic authentication using the API username and password from the Messente dashboard API settings.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

Number Verification 2

PIN-based phone number verification (2FA / one-time passwords).

POST
/verify/start
Initiates phone number verification
verifyNumber body → 200
POST
/verify/pin
Verifies a PIN code
verifyPin body → 200400

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Viber (7 properties), SMS (5 properties), OmniMessageCreateSuccessResponse (3 properties), Omnimessage (3 properties). Each schema is shown below with its type and property counts.

WhatsApp
object
A WhatsApp channel message.
3 properties
WhatsAppText
object
2 properties
Omnimessage
object
A message delivered over one or more channels. The messages array defines the fallback chain in priority order.
3 properties 2 required
Viber
object
A Viber channel message.
7 properties 1 required
SMS
object
An SMS channel message.
5 properties 1 required
OmniMessageCreateSuccessResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

messente-number-verification-api-openapi.yml Raw ↑

Other APIs Messente publishes across the network.

Messente Account Balance API
Messente Blacklist API
Messente Bulk Messaging API
Messente Contacts API
Messente Delivery Report API
Messente Groups API
Messente Number Lookup API
Messente Omnimessage API
Messente Pricing API
Messente Statistics API
Where this information came from

This is an independent, third-party profile of Messente Number Verification API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.