GSMA
The GSMA (GSM Association) is the London-headquartered global trade body for the mobile industry, representing roughly 750 mobile network operators and around 400 companies in the wider mobile ecosystem, and the organiser of MWC Barcelona. In telecom's API value chain the GSMA is not a network operator and not an aggregator; it is the standards and commitment layer. Its GSMA Open Gateway initiative is the memorandum of understanding under which 69 operator groups, representing 78% of global mobile connections, commit to exposing a common set of network APIs, while the API specifications themselves are authored in the Linux Foundation's CAMARA project. The GSMA's API posture is unusually open for a standards body: its Open Gateway developer portal at open-gateway.gsma.com publishes 17 CAMARA OpenAPI 3.0.3 documents in full, without login, alongside a live public deployment map covering 607 launched API instances across 80 operators and 65 countries, and it runs a separate, fully open Mobile Money API developer portal with a downloadable OpenAPI 3.0.0 specification, SDKs, and use-case guides. The gates are real but narrow: the API sandbox requires a GitHub sign-in, the anti-fraud Scam Signal API is held in a private GSMA repository rather than in public CAMARA, and the commercial GSMA Services products (Device Check, IMEI Database, PathFinder, Disposable Number Check) are membership and contract gated with no public documentation. The GSMA runs no production network API endpoints of its own — every Open Gateway API is served by an operator or a channel partner such as Infobip, IPification, TMT iD, XConnect, or Singtel.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles GSMA the way a machine reads it — 55 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — GSMA scores 57.0/100 (strong), with a separate agent-readiness read of 41/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from GSMA's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/gsma/"
title="GSMA on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/gsma.svg"
alt="GSMA Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/gsma/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/gsma/"
title="GSMA on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/gsma/card.svg"
alt="GSMA Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile GSMA
Each block below is one kind of artifact we hold for GSMA. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 31
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
GSMA Accounts API
The **Accounts** APIs are used to support a range of operations on a financial account resource and associated resources. Types of accounts include mobile wallets, financial ins...
GSMA Authorisation Codes API
The **Authorisation** Codes APIs allow a payer to generate a payment code which when presented to the payee, can be redeemed for an amount associated with the code. Authorisatio...
GSMA Bills API
The **Bills** APIs allow a mobile money provider to allow customers to retrieve and pay bills. Specific use cases include: - Retrieving information on service providers (bill co...
GSMA Call Forwarding information retrieval API
Provides information on Call Forwarding settings for the provided phone number (PhoneNumber).
GSMA Check Device Swap API
Validate if the SIM of the end-user has been installed in a different device during a past period
GSMA Check SIM Swap API
operation to perform a sim swap check for a past period
GSMA Debit Mandates API
The **Debit Mandates** APIs allow a mobile money customer to provide prior approval for payments to be taken from their account by a requesting payee. If the amount limit field ...
GSMA Device reachability status API
Operations to get the current reachability status of a device
GSMA Discovery API
Find the closest Edge Cloud Zone to the user device.
GSMA Get Device Identifiers API
Retrieve details about the device being used by a mobile subscriber
GSMA Home Devices QoD API
QoD control operations for home devices
GSMA Links API
The **Links** APIs are used to establish a link between two separate accounts on the client and provider systems. The API can be used for example to link a mobile wallet account...
GSMA Location Retrieval API
Retrieve the location of a device
GSMA Location Verification API
Verification of the location of a device
GSMA Match API
Operations to match a customer identity against the account data bound to their phone number.
GSMA One Step Payment API
Operations to manage One Step Payment procedure
GSMA OTP Management API
API operations to manage OTP codes
GSMA Payment API
Operations to obtain information about payments
GSMA Phone Number Share API
API operation to return the phone number associated to the access token.
GSMA Phone Number Verify API
API operation to verify a phone number received as input. It can be received either in plain text or hashed format.
GSMA Population Density Data API
Operations to retrieve population density information.
GSMA QoS Sessions API
Manage QoS sessions
GSMA Quotations API
The **Quotations** APIs are used to obtain one or multiple quotes for a mobile money customer who wishes to transfer money. The creation of a quote involves returning any fees t...
GSMA Refund API
Operations to manage Refund procedure
GSMA Retrieve Device Swap Date API
Receive the last date in which the device of the end-user was swapped
GSMA Retrieve SIM Swap Date API
operation to retrieve latest SIM swap change date
GSMA Roaming status retrieval API
Operation to get device roaming status and country information (if roaming) synchronously
GSMA Supporting API
Supporting APIs consist of the following: - **Heartbeat API:** Used for monitoring purposes and establishes whether the system of an API provider is in a state that enables a cl...
GSMA Transactions API
The **Transactions** APIs are used to support mobile money financial transaction use cases. Transactions are used for a wide range of use cases including merchant payments, inte...
GSMA Two Step Payment API
Operations to manage Two Step Payment procedure
GSMA Unconditional Call Forwarding information retrieval API
Provides information on Unconditional Call Forwarding settings for the provided phone number (PhoneNumber)
Scroll within the panel for all 31 ·
Open Collections 18
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Mobile Money API
OPEN COLLECTIONCall Forwarding Signal
OPEN COLLECTIONCarrier Billing Refund
OPEN COLLECTIONCarrier Billing
OPEN COLLECTIONCAMARA Mobile Device Identifier
OPEN COLLECTIONDevice Location Retrieval
OPEN COLLECTIONDevice Location Verification
OPEN COLLECTIONDevice Reachability Status
OPEN COLLECTIONDevice Roaming Status
OPEN COLLECTIONDevice Swap
OPEN COLLECTIONHome Devices QoD
OPEN COLLECTIONKnow Your Customer Match
OPEN COLLECTIONNumber Verification
OPEN COLLECTIONOne Time Password SMS
OPEN COLLECTIONPopulation Density Data
OPEN COLLECTIONQuality-On-Demand
OPEN COLLECTIONSIM Swap
OPEN COLLECTIONSimple Edge Discovery
OPEN COLLECTIONScroll within the panel for all 18 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Gsma Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for GSMA — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 7
Portal, sign-up, and the first successful call
Scroll within the panel for all 7 ·
Documentation 8
Reference material describing how the API behaves
Scroll within the panel for all 8 ·
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 5
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/gsma · machine-readable index on apis.io
This is an independent, third-party profile of GSMA, 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.