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 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 client to submit a request for processing within established SLAs.- **Request State API** : Used to determine the state of an asynchronous request.- **Responses API** : In some circumstances, the client may not have received the final representation of the resource for which it attempted to create or update. The **Responses** API allows a client to identify and retrieve the final representation of the resource assuming that the resource was created.

GSMA Supporting API is one of 31 APIs that GSMA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 3 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.2.0.

Requests are made against a single base URL, https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm.

4 operations 3 paths 12 schemas 3 GET1 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2.0
Base URL
https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
Resource Areas
1

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 3 GET, 1 PATCH. Each is listed below with its method, path, parameters, and response codes.

Supporting 4

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 client t…

GET
/heartbeat
Check API availability
heartbeatGET 3 params → 200400401404500503
GET
/requeststates/{serverCorrelationId}
View A Request State
requeststatesServerCorrelationIdGET 8 params → 200400401404500503
PATCH
/requeststates/{serverCorrelationId}deprecated
Update A Request State
requeststatesServerCorrelationIdPATCH 9 params body → 204400401404500503
GET
/responses/{clientCorrelationId}
View A Response
responsesClientCorrelationIdGET 8 params → 200400401404500503

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are requestStateObject (8 properties), errorObject (5 properties), responseHeartbeat (3 properties), requestGenericPatch (3 properties). Each schema is shown below with its type and property counts.

responseResponse
object
1 property 1 required
metadata
object
2 properties 2 required
requestGenericPatch
object
3 properties 3 required
serviceStatus
string
Provides the status of the requested service.
metadataArray
array
A collection of key/value pairs. These can be used to populate additional properties that describe administrative information regarding the resource.
delay
number
The anticipated processing delay in milliseconds.
requestGenericPatchArray
array
Collection of updates that are to be processed.
requestStateObject
object
8 properties 3 required
link
string
Provides a URL to the resource.
responseHeartbeat
object
3 properties 1 required
errorObject
object
5 properties 2 required
plannedRestorationTime
string
Where the planned restoration time is known (e.g. scheduled maintenance), it can be provided in this field.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gsma-supporting-api-openapi.yml Raw ↑

Other APIs GSMA publishes across the network.

GSMA Accounts API
GSMA Authorisation Codes API
GSMA Bills API
GSMA Call Forwarding information retrieval API
GSMA Check Device Swap API
GSMA Check SIM Swap API
GSMA Debit Mandates API
GSMA Device reachability status API
GSMA Discovery API
GSMA Get Device Identifiers API
GSMA Home Devices QoD API
GSMA Links API
Where this information came from

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