GSMA website screenshot

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.

GSMA publishes 31 APIs on the APIs.io network, including Accounts API, Authorisation Codes API, Bills API, and 28 more. Tagged areas include Telecommunications, United Kingdom, Standards, Trade Association, and Network APIs.

The GSMA catalog on APIs.io includes 1 event-driven AsyncAPI specification.

GSMA’s developer surface includes authentication, documentation, sandbox, YouTube channel, changelog, API reference, getting-started guide, and 49 more developer resources.

🌐 Visit website 📡 Source on GitHub
54.9/100 strong ▬ flat Agent 41/100 agent native saas Full breakdown ↓
scored 2026-09-06 · rubric v0.19.0
18 APIs
TelecommunicationsUnited KingdomStandardsTrade AssociationNetwork APIsCAMARAOpen GatewayMobile Network OperatorsIdentity VerificationSIM SwapMobile MoneyeSIM5GAnti-FraudSpecification

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-06 · rubric v0.19.0
Composite quality — 54.9/100 · strong
Contract Quality 12.5 / 21
Developer Ergonomics 12.4 / 17
Access Clarity 4.0 / 17
Operational Transparency 4.9 / 11
Contract Governance 0.5 / 10
Discoverability 5.8 / 9
Regulatory Posture 12.1 / 15
Agent readiness — 41/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 6 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 6 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Telecommunications regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/gsma: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 31

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 for all 31

Open Collections 18

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Mobile Money API

OPEN COLLECTION

Call Forwarding Signal

OPEN COLLECTION

Carrier Billing Refund

OPEN COLLECTION

Carrier Billing

OPEN COLLECTION

CAMARA Mobile Device Identifier

OPEN COLLECTION

Device Location Retrieval

OPEN COLLECTION

Device Location Verification

OPEN COLLECTION

Device Reachability Status

OPEN COLLECTION

Device Roaming Status

OPEN COLLECTION

Device Swap

OPEN COLLECTION

Home Devices QoD

OPEN COLLECTION

Know Your Customer Match

OPEN COLLECTION

Number Verification

OPEN COLLECTION

One Time Password SMS

OPEN COLLECTION

Population Density Data

OPEN COLLECTION

Quality-On-Demand

OPEN COLLECTION

SIM Swap

OPEN COLLECTION

Simple Edge Discovery

OPEN COLLECTION

Scroll for all 18

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Gsma Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Gsma Authentication

http/openIdConnect/unknown · 3 schemes

SECURITY

Gsma Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Gsma Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Gsma Scopes

30 scopes

30 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Gsma Agentic Access

107 operations · 58 acting

107 operations · 58 acting

AGENTIC

Resources

Get Started 7

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 Sandbox
Sandbox
 Sandbox
Sandbox
 GettingStarted
GettingStarted
 SignUp
SignUp
 Login
Login
 DeveloperPortal
DeveloperPortal

Scroll for all 7

Documentation 8

Reference material describing how the API behaves

Documentation
Documentation
 Documentation
Documentation
 Documentation
Documentation
 Documentation
Documentation
 Documentation
Documentation
 Documentation
Documentation
 Specification
Specification
 APIReference
APIReference

Scroll for all 8

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess
AgenticAccess
 WellKnown
WellKnown
 LLMsTxt
LLMsTxt
 X-MCPServerCandidate
X-MCPServerCandidate
 AgentSkill
AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 Conventions
Conventions
 Idempotency
Idempotency
 DataModel
DataModel
 Webhooks
Webhooks

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 GitHubOrganization
GitHubOrganization
 Packages
Packages
 SDKs
SDKs

Access & Security 6

Authentication, authorization, and security posture

VulnerabilityDisclosure
VulnerabilityDisclosure
 DomainSecurity
DomainSecurity
 Authentication
Authentication
 SecurityTxt
SecurityTxt
 Security
Security
 OAuthScopes
OAuthScopes

Learn 1

Tutorials, courses, talks, and written guidance

YouTube
YouTube

Operate 5

Status, limits, changes, and where to get help

Deprecation
Deprecation
 ChangeLog
ChangeLog
 ChangeLog
ChangeLog
 Support
Support
 FAQ
FAQ

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 5

The organization behind the API

Website
Website
 LinkedIn
LinkedIn
 Twitter
Twitter
 Newsroom
Newsroom
 Blog
Blog

Other 6

Properties that don't map to a standard resource type

CapabilityMap
CapabilityMap
 Overlay
Overlay
 Dataset
Dataset
 Services
Services
 Membership
Membership
 Glossary
Glossary

Source (apis.yml)

apis.yml Raw ↑ 
aid: gsma
url: https://raw.githubusercontent.com/api-evangelist/gsma/refs/heads/main/apis.yml
name: GSMA
kind: company
description: '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.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Telecommunications
- United Kingdom
- Standards
- Trade Association
- Network APIs
- CAMARA
- Open Gateway
- Mobile Network Operators
- Identity Verification
- SIM Swap
- Mobile Money
- eSIM
- 5G
- Anti-Fraud
- Specification
created: '2026-07-25'
modified: '2026-07-25'
specificationVersion: '0.23'
apis:
- aid: gsma:gsma-accounts-api
  name: GSMA Accounts API
  description: '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 institution accounts and utility accounts (e.g. for electricity).


    **Identifying a Target Account**


    Two methods are provided for identifying an account, the single identifier method and the multiple identifiers method.


    Single Identifier Method:


    - In the scenario where one identifier suffices to uniquely identify an account, the following path is to be used: **/accounts/{identifierType}/{identifier}**.


    Multiple Identifiers Method:


    - Where a single identifier is not sufficient to identify an account, the following path is to be used: ' **/accounts/{accountIdentifier1}@{value1}${accountIdentifier2}@{value2}${accountIdentifier3}@{value3}**'.
    The list of permitted account identifiers supported by the Mobile Money API can be found in the API documentation. As
    there can be multiple identifiers required to identify the target account, the path uses a '$' delimiter to separate
    each identifier, up to a limit of three account identifiers.'
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Account
  tags_raw:
  - Accounts
  properties:
  - type: OpenAPI
    url: openapi/gsma-accounts-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-authorisation-codes-api
  name: GSMA Authorisation Codes API
  description: '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.

    Authorisation codes can be set to expire. Note that expiry time can be specified via the API, however the mobile money
    provider

    may mandate a common expiry period for all codes.

    Authorisation Codes are used widely in the industry across a range of use cases, including:


    - ATM Codes for card-less withdrawals. A code is generated in advance by the customer and entered into the ATM to facilitate
    the withdrawal.

    - Pre-authorised codes for agent withdrawals. A code is generated in advance by the customer and given to the agent to
    facilitate the withdrawal.

    - Pre-authorised codes for merchant payments. The customer generates a code which can be redeemed at a merchant.'
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Authorisation Codes
  properties:
  - type: OpenAPI
    url: openapi/gsma-authorisation-codes-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-bills-api
  name: GSMA Bills API
  description: '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 companies) that accept bill payments.

    - Retrieving bills at a service provider for a given mobile money customer.

    - Allowing mobile money customers to partially or fully pay bills for a service provider.

    - Retrieving bill payment information from a service provider for a given customer.'
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Bills
  properties:
  - type: OpenAPI
    url: openapi/gsma-bills-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-call-forwarding-information-retrieval-api
  name: GSMA Call Forwarding information retrieval API
  description: Provides information on Call Forwarding settings for the provided phone number (PhoneNumber).
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Call Forwarding information retrieval
  tags_raw:
  - Call Forwarding information retrieval
  properties:
  - type: OpenAPI
    url: openapi/gsma-call-forwarding-information-retrieval-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-check-device-swap-api
  name: GSMA Check Device Swap API
  description: Validate if the SIM of the end-user has been installed in a different device during a past period
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Check Device Swap
  properties:
  - type: OpenAPI
    url: openapi/gsma-check-device-swap-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-check-sim-swap-api
  name: GSMA Check SIM Swap API
  description: operation to perform a sim swap check for a past period
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Check SIM swap
  tags_raw:
  - Check SIM Swap
  properties:
  - type: OpenAPI
    url: openapi/gsma-check-sim-swap-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-debit-mandates-api
  name: GSMA Debit Mandates API
  description: '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 is not supplied, the payee will be able to take any amount. Mandates can
    be open-ended

    or can be constrained by a quantified number of payments for a given frequency.


    Mandates can be created, viewed and modified. The request to create a debit mandate will be typically initiated by the

    service provider (payee) but can also be requested by the customer (payer).'
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Debit Mandates
  properties:
  - type: OpenAPI
    url: openapi/gsma-debit-mandates-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-device-reachability-status-api
  name: GSMA Device reachability status API
  description: Operations to get the current reachability status of a device
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Device reachability status
  properties:
  - type: OpenAPI
    url: openapi/gsma-device-reachability-status-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-discovery-api
  name: GSMA Discovery API
  description: Find the closest Edge Cloud Zone to the user device.
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Discovery
  properties:
  - type: OpenAPI
    url: openapi/gsma-discovery-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-get-device-identifiers-api
  name: GSMA Get Device Identifiers API
  description: Retrieve details about the device being used by a mobile subscriber
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Get Device Identifiers
  properties:
  - type: OpenAPI
    url: openapi/gsma-get-device-identifiers-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-home-devices-qod-api
  name: GSMA Home Devices QoD API
  description: QoD control operations for home devices
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Home Devices QoD
  properties:
  - type: OpenAPI
    url: openapi/gsma-home-devices-qod-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-links-api
  name: GSMA Links API
  description: '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 to a Microfinance Institution account or a bank account.
    The link object does not mandate the processes to verify and authenticate a link request - this depends upon the use case.
    A link needs to be associated with a mode of operation:


    - pull. The link can be used by the client to debit the target account held by the provider.

    - push. The link can be used by the client to credit the target account held by the provider.

    - both. The link can be used for Push and Pull requests.'
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Links
  properties:
  - type: OpenAPI
    url: openapi/gsma-links-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-location-retrieval-api
  name: GSMA Location Retrieval API
  description: Retrieve the location of a device
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Location retrieval
  tags_raw:
  - Location Retrieval
  properties:
  - type: OpenAPI
    url: openapi/gsma-location-retrieval-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-location-verification-api
  name: GSMA Location Verification API
  description: Verification of the location of a device
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Location Verification
  properties:
  - type: OpenAPI
    url: openapi/gsma-location-verification-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-match-api
  name: GSMA Match API
  description: Operations to match a customer identity against the account data bound to their phone number.
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Match
  properties:
  - type: OpenAPI
    url: openapi/gsma-match-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-one-step-payment-api
  name: GSMA One Step Payment API
  description: Operations to manage One Step Payment procedure
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - One Step Payment
  properties:
  - type: OpenAPI
    url: openapi/gsma-one-step-payment-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-otp-management-api
  name: GSMA OTP Management API
  description: API operations to manage OTP codes
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - OTP Management
  properties:
  - type: OpenAPI
    url: openapi/gsma-otp-management-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-payment-api
  name: GSMA Payment API
  description: Operations to obtain information about payments
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Payment
  properties:
  - type: OpenAPI
    url: openapi/gsma-payment-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-phone-number-share-api
  name: GSMA Phone Number Share API
  description: API operation to return the phone number associated to the access token.
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Phone number share
  tags_raw:
  - Phone Number Share
  properties:
  - type: OpenAPI
    url: openapi/gsma-phone-number-share-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-phone-number-verify-api
  name: GSMA Phone Number Verify API
  description: API operation to verify a phone number received as input. It can be received either in plain text or hashed
    format.
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Phone number verify
  tags_raw:
  - Phone Number Verify
  properties:
  - type: OpenAPI
    url: openapi/gsma-phone-number-verify-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/change-list.html
  - type: Idempotency
    url: conventions/gsma-conventions.yml
- aid: gsma:gsma-population-density-data-api
  name: GSMA Population Density Data API
  description: Operations to retrieve population density information.
  humanURL: https://developer.mobilemoneyapi.io/api-versions-1.2/
  baseURL: https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
  tags:
  - Population Density Data
  properties:
  - type: OpenAPI
    url: openapi/gsma-population-density-data-api-openapi.yml
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/
  - type: APIReference
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/api-service-definition.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/api-versions-1.2/resources/open-oas3-ui.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/sdks/getting-started/introduction.html
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/security/
  - type: Documentation
    url: https://developer.mobilemoneyapi.io/guidelines/
  - type: Webhooks
    url: asyncapi/gsma-webhooks.yml
  - type: SDKs
    url: packages/gsma-packages.yml
  - type: ChangeLog
    url: https://developer.mobilemon

# --- truncated at 32 KB (50 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/gsma/refs/heads/main/apis.yml

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/gsma"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/gsma/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/gsma/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.