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

Mavenir BYON Registration and Connectivity Management (RACM) API

A Mavenir-authored OpenAPI 3.0.0 definition for Bring Your Own Number (BYON) Registration and Connectivity Management, giving a REST client the ability to register into and manage its connectivity toward a mobile network operator's IMS network. Four operations create, refresh and delete a RACM session and register a push channel. Contributed by Mavenir to the CAMARA API Backlog as a supporting document for the WebRTC API proposal; it is a standards-track reference definition, not a hosted Mavenir endpoint, with a templated {apiRoot} server defaulting to http://localhost:9091 and HTTP Bearer authentication.

Mavenir BYON Registration and Connectivity Management (RACM) API is one of 3 APIs that Mavenir publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include IMS, Registration, Connectivity, WebRTC, and CAMARA. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 3 paths, organized into 2 resource areas, and defines 6 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against a single base URL, {apiRoot}/racm/{apiVersion}/{userId}.

4 operations 3 paths 6 schemas 1 DELETE2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Server
{apiRoot}/racm/{apiVersion}/{userId}
Authentication
HTTP Bearer
Resource Areas
2

Authentication & Security 1

Mavenir BYON Registration and Connectivity Management (RACM) API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth).

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 DELETE, 2 POST, 1 PUT. They span 2 resource areas: RACM, Push Token. Each is listed below with its method, path, parameters, and response codes.

RACM 3
POST
/session
Create RACM Session
1 param body → 200400
PUT
/session/{sessionId}
For sharing new AccessToken with WebRTC GW, the AccessToken is expected to be received from the Auth server.
3 params → 200
DELETE
/session/{sessionId}
Delete Registration Session.
3 params → 204400
Push Token 1
POST
/push
Update device token
2 params body → 200400403

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are PushInformation (6 properties), ErrorInfo (3 properties), RacmResponse (3 properties), ConnectionInformation (1 property). Each schema is shown below with its type and property counts.

RacmRequest
object
1 property
RacmResponse
object
3 properties
NotificationChannelInformation
object
1 property
ConnectionInformation
object
1 property
PushInformation
object
6 properties 1 required
ErrorInfo
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mavenir-byon-racm-openapi.yml Raw ↑

Other APIs Mavenir publishes across the network.

Mavenir BYON Call Handling API (VVoIP Service)
Mavenir Digital Enablement (MDE) TM Forum Open APIs
Where this information came from

This is an independent, third-party profile of Mavenir BYON Registration and Connectivity Management (RACM) 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.