This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with 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 so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
Mavenir is a US-headquartered (Richardson, Texas) cloud-native telecom network software vendor that builds the software operators run rather than a network or a developer platform of its own. Its portfolio spans Open RAN and vRAN (MAVair), converged packet core and cloud-native IMS (MAVcore), messaging, fraud and security applications, the Mavenir Digital Enablement (MDE) BSS and converged charging stack (MAVapps), private networks, MEC and an Intelligent IoT Platform (MAVedge). In the telecom value chain Mavenir sits upstream of the carrier — it supplies the Combo NEF/SCEF network-exposure function and the BSS that a mobile operator uses to expose and monetize CAMARA and GSMA Open Gateway network APIs, but it does not expose those APIs to developers itself.
APIs.json: https://raw.githubusercontent.com/api-evangelist/mavenir/refs/heads/main/apis.yml
There is no Mavenir developer portal. developer.mavenir.com, developers.mavenir.com, docs.mavenir.com, api.mavenir.com, apis.mavenir.com, opengateway.mavenir.com, nef.mavenir.com and exposure.mavenir.com all fail to resolve. /developer, /developers, /api and /open-gateway on the corporate site all return 404. The full sitemap (86 pages, 360 press releases, 194 resources) contains zero developer or API-reference pages. The only live gated surface, support.mavenir.com, 307-redirects to an ADFS SSO login wall for existing customers.
Mavenir hosts no downloadable specification. /openapi.json, /swagger.json and /api-docs all 404, and no OpenID Connect or OAuth discovery document is served.
What is real and public is Mavenir's standards work.
Active CAMARA contributor and co-maintainer, not a CAMARA API exposer. This is not a press release — it is code and governance in the camaraproject GitHub organization:
- Eleven Mavenir individuals are listed in camaraproject/Governance PARTICIPANTS.MD.
- Mavenir appears in the CAMARA landscape as a Solution Provider / Network Capability Solution Provider.
- Two Mavenir engineers are listed in camaraproject/WebRTC MAINTAINERS.MD, and
@pradeepachar-maveniris a default CODEOWNER of the whole repository. - The CAMARA API Backlog lists Mavenir as a supporter of the WebRTC API alongside GSMA-OGW, Orange, Telefónica, T-Mobile US and Vodafone.
CAMARA APIs with real Mavenir evidence: WebRTC Call Handling, WebRTC Events / Subscriptions, WebRTC Registration. No evidence was found that Mavenir exposes any of the commercial CAMARA APIs (Number Verification, SIM Swap, Device Location, Device Status, Quality on Demand, Carrier Billing, KYC Match, Scam Signal, Device Swap, Population Density) — it supplies the operators who do.
GSMA Open Gateway: Mavenir is not an operator and is not on the GSMA operator list. Its 2024-12-18 Spry Fox Networks release states that the partner's QP Cloud MONET is "the first Channel Partner Solution to become certified with Open Gateway API Certification" and that "Mavenir's Combo NEF/SCEF ... provides exposure of standard defined network APIs to third-party applications via QPCM." The certification belongs to the partner. No Aduna relationship was found.
| Level | Product | APIs | Date |
|---|---|---|---|
| Platinum | Mavenir Digital Enablement (MDE) BSS | 20+ certified Open APIs (numbers not itemized in the announcement) | 2023-09-20 |
| Silver | Cloud-native BSS suite | TMF620 Product Catalog, TMF622 Product Ordering, TMF629 Customer Management, TMF632 Party Management, TMF667 Document Management | 2022-10-06 |
Mavenir sells a Combo NEF/SCEF (Network Exposure Function / Service Capability Exposure Function) and publishes a resource, Monetizing 5G SA with the Network Exposure Function, describing exposure of 5G SA capability to third-party applications with usage-based charging and tiered QoS pricing. MEC, private networks/CBRS, IIoTP and network slicing are all productized. None of it has a public API surface.
HTTP Bearer in Mavenir's own contributed definitions; OpenID Connect in the CAMARA WebRTC definitions Mavenir co-maintains. CIBA does not appear anywhere — not in the Mavenir BYON specs, not in the CAMARA WebRTC specs, not on mavenir.com.
A Mavenir-authored OpenAPI 3.0.0 definition for Bring Your Own Number one-to-one voice and video calling over WebRTC, contributed by Mavenir (contact@mavenir.com, Apache 2.0) to the CAMARA API Backlog. Four operations. A contributed reference definition in a public standards repository, not a Mavenir-hosted commercial endpoint.
- Human URL: CAMARA APIBacklog — BYON-CallHandling-Service.yaml
- OpenAPI: openapi/mavenir-byon-call-handling-openapi.yml
A Mavenir-authored OpenAPI 3.0.0 definition letting a REST client register into and manage connectivity toward an operator's IMS network. Four operations, including a push-channel registration. Also a CAMARA API Backlog supporting document.
- Human URL: CAMARA APIBacklog — BYON-RACM-Service.yaml
- OpenAPI: openapi/mavenir-byon-racm-openapi.yml
The TM Forum Open APIs implemented in Mavenir's cloud-native BSS, converged charging and digital marketplace platform, certified Platinum with 20+ Open APIs. The certification is real and verifiable; Mavenir publishes no API reference, no OpenAPI download and no endpoint for them. They ship inside a licensed operator deployment.
- Human URL: Mavenir Digital Enablement BSS
None. github.com/mavenir exposes no public repositories, there is no PyPI or npm organization, no SwaggerHub owner, no public Postman workspace, no GraphQL surface and no published event or webhook catalog.
- Telecommunications
- United States
- Network Vendor
- Network APIs
- CAMARA
- Open Gateway
- BSS
- OSS
- TM Forum
- Open RAN
- 5G
- IMS
- Messaging
- Network Exposure Function
- Standards
- Created: 2026-07-25
- Modified: 2026-07-25