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

GSMA Number Verification

GSMA Number Verification from GSMA — 2 path(s) described in OpenAPI.

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

The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, organized into 2 resource areas, and defines 5 schemas. It is described by OpenAPI 3.0.3, at version wip.

Requests are made against a single base URL, {apiRoot}/number-verification/vwip.

2 operations 2 paths 5 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
wip
Base URL
https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
Authentication
OpenID Connect
License
Resource Areas
2

Authentication & Security 1

GSMA Number Verification declares 1 security scheme for authenticating requests. It supports OpenID Connect (openId) discovered at https://example.com/.well-known/openid-configuration.

  • openId — OpenID Connect authentication.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. They span 2 resource areas: Phone Number Verify, Phone Number Share. Each is listed below with its method, path, parameters, and response codes.

Phone Number Verify 1

API operation to verify a phone number received as input. It can be received either in plain text or hashed format.

POST
/verify
Verifies if the received hashed/plain text phone number matches the phone number associated with the access token
phoneNumberVerify 1 param body → 200400401403
Phone Number Share 1

API operation to return the phone number associated to the access token.

GET
/device-phone-number
Returns the phone number associated with the access token
phoneNumberShare 1 param → 200400401403

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are NumberVerificationRequestBody (2 properties), NumberVerificationShareResponse (1 property), NumberVerificationMatchResponse (1 property). Each schema is shown below with its type and property counts.

NumberVerificationRequestBody
object
Payload to verify the phone number.
2 properties
NumberVerificationMatchResponse
object
Number verification result
1 property 1 required
NumberVerificationShareResponse
object
Number verification share result
1 property 1 required
DevicePhoneNumber
DevicePhoneNumberVerified
boolean
Number verification. True, if it matches

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gsma-open-gateway-number-verification-openapi.yml Raw ↑

Other APIs GSMA publishes across the network.

GSMA Mobile Money API
GSMA Call Forwarding Signal
GSMA Carrier Billing
GSMA Carrier Billing Refund
GSMA CAMARA Mobile Device Identifier
GSMA Device Location Retrieval
GSMA Device Location Verification
GSMA Device Reachability Status
GSMA Device Roaming Status
GSMA Device Swap
GSMA Home Devices QoD
GSMA Know Your Customer Match
Where this information came from

This is an independent, third-party profile of GSMA Number Verification, 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.