GSMA Carrier Billing
GSMA Carrier Billing from GSMA — 6 path(s) described in OpenAPI.
GSMA Carrier Billing 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 7 operations across 6 paths, organized into 3 resource areas, and defines 41 schemas. It is described by OpenAPI 3.0.3, at version wip.
Requests are made against a single base URL, {apiRoot}/carrier-billing/vwip.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
GSMA Carrier Billing declares
2 security schemes
for authenticating requests.
It supports OpenID Connect (openId) discovered at https://example.com/.well-known/openid-configuration.
It accepts HTTP bearer tokens ({$request.body#/sinkCredential.credentialType}) (notificationsBearerAuth).
Paths & Operations 7
Across 6 paths, the API surfaces 7 operations — 2 GET, 5 POST. They span 3 resource areas: One Step Payment, Payment, Two Step Payment. Each is listed below with its method, path, parameters, and response codes.
Operations to manage One Step Payment procedure
Operations to obtain information about payments
Operations to manage Two Step Payment procedure
Schemas 41
The contract defines 41 schemas that model the data the API accepts and returns. The most detailed are ChargingMetaData (7 properties), CloudEvent (7 properties), PaymentCreated (6 properties), Payment (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from GSMA 12
Other APIs GSMA publishes across the network.
This is an independent, third-party profile of GSMA Carrier Billing, 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.