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 Traffic Influence API Read API

Reads existing TrafficInfluence resources

GSMA Traffic Influence API Read API is one of 41 APIs that GSMA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Traffic Influence API Read. The published artifact set on APIs.io includes an OpenAPI specification, a GitHub repository, API documentation, and an API reference.

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

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

2 operations 2 paths 15 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

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

  • openId — to support Consent Management

Paths & Operations 2

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

Traffic Influence API Read 2

Reads existing TrafficInfluence resources

GET
/traffic-influences
Global System for Mobile Communications Retries existing TrafficInfluence…
getTrafficInfluence 2 params → 200401403500503504
GET
/traffic-influences/{trafficInfluenceID}
Global System for Mobile Communications Reads a specific TrafficInfluence…
getAllTrafficInfluences 2 params → 200401403404500503504

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are TrafficInfluence (12 properties), Device (4 properties), DeviceIpv4Addr (3 properties), ErrResponse (2 properties). Each schema is shown below with its type and property counts.

Protocol
string
The protocol for the influeced flow. It can be specified and it is identified by a string according to the column Keyword as defined by IANA (https://www.iana.…
ErrorInfo
object
Information in case of error
2 properties 2 required
DeviceIpv4Addr
object
The device should be identified by either the public (observed) IP address and port as seen by the application server, or the private (local) and any public (o…
3 properties
TrafficInfluence
object
Resource conteining the informations to influence the traffic from the device to the EAS
12 properties 2 required
ErrResponse
object
Responce feedback in case of errors
2 properties
SingleIpv4Addr
string
A single IPv4 address with no subnet mask
DeviceIpv6Address
string
The device should be identified by the observed IPv6 address, or by any single IPv6 address from within the subnet allocated to the device (e.g. adding ::0 to…
Port
integer
TCP or UDP port number
AppInstanceId
string
A globally unique identifier associated with a running instance of an application. OP generates this identifier.
Device
object
End-user equipment able to connect to a mobile network. Examples of devices include smartphones or IoT sensors/actuators. The developer can choose to provide t…
4 properties
EdgeCloudZoneId
string
Unique identifier created by the Edge Cloud Platform to identify an Edge Cloud Zone within an Edge Cloud
AppId
string
A globally unique identifier associated with theapplication. OP generates this identifier when the application is submitted over NBI.
EdgeCloudRegion
string
Human readable name of the geographical Edge Cloud Region of the Edge Cloud. Defined by the Edge Cloud Provider.
NetworkAccessIdentifier
string
A public identifier addressing a subscription in a mobile network. In 3GPP terminology, it corresponds to the GPSI formatted with the External Identifier ({Loc…
PhoneNumber
string
A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Num…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gsma-traffic-influence-api-read-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 Debit Mandates API
GSMA Discovery API
GSMA Home Devices QoD API
GSMA Links API
GSMA Location Retrieval API
GSMA Match API
GSMA One Step Payment API
Where this information came from

This is an independent, third-party profile of GSMA Traffic Influence API Read 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.