Answers
What Are TM Forum Open APIs and Why Do They Matter for BSS Integration?
TM Forum Open APIs are standard REST interfaces for telecom business and operations systems, published by TM Forum, the industry association for communications service providers and their suppliers. Each API covers one business function, such as the product catalogue, ordering, customer records, billing or usage, and defines the same endpoints and data model whichever vendor implements it.
They matter because integration between BSS and OSS components is one of the biggest costs in telecom IT. If both sides speak the same standard API, connecting them takes less custom work, and replacing one component does not mean rebuilding every connection to it.
How the APIs are organised
Each API has a TMF number and a version, for example TMF622 v4. They use REST and JSON, share a common data model, and form part of TM Forum's Open Digital Architecture (ODA), its reference model for building telecom IT from interchangeable components.
The APIs most relevant to BSS integration:
| API | Function |
|---|---|
| TMF620 Product Catalog | Product offerings, specifications and prices |
| TMF622 Product Ordering | Placing and tracking customer orders |
| TMF629 Customer Management | Customer records |
| TMF632 Party Management | People and organisations the operator deals with |
| TMF666 Account Management | Billing and financial accounts |
| TMF678 Customer Bill Management | Bills and bill details |
| TMF635 Usage Management | Usage records |
| TMF637 Product Inventory | What each customer currently has |
| TMF641 Service Ordering | Turning product orders into service tasks |
| TMF621 Trouble Ticket | Faults and support tickets |
| TMF679 Product Offering Qualification | Checking whether an offer is available to a customer or location |
An order, through the APIs
A typical order moves through the standard interfaces like this:
- A sales channel reads available offers from the catalogue (TMF620).
- It submits the customer's order (TMF622).
- Order management breaks the order into service tasks (TMF641).
- Service management requests the resources it needs (TMF652) and activates the service (TMF640).
- Product, service and resource inventories are updated (TMF637, TMF638, TMF639).
Why it matters for MVNOs and MVNAs
Virtual operators depend on integration more than most. An MVNO's stack connects to a host network, an MVNE or MVNA, payment providers, eSIM platforms, CRM, retail and partner channels. An MVNA connects to many MVNOs at once. Every custom interface is a project to build and a dependency to maintain.
Standard APIs help in three ways:
- Faster partner onboarding. A partner that already uses TMF622 or TMF620 can connect with mapping work rather than a new integration.
- Less lock-in. Components behind standard interfaces are easier to replace.
- Clearer vendor comparison. "Which TMF APIs do you support, at which version?" is a concrete question with a checkable answer.
What conformance does and does not prove
TM Forum runs a conformance programme. Vendors can self-certify, or run TM Forum's conformance test kit against their implementation.
Conformance confirms structural compatibility: correct endpoints, data models and operations. It does not guarantee semantic interoperability. Two systems can both implement TMF622 and still disagree on what an order status means or how order items are structured. Integration still needs mapping and testing. It just starts from a much closer position.
Questions to ask a BSS vendor
For TelcoEdge's own API layer, see Edge API.
- Which TMF APIs do you expose, and at which version?
- Is conformance self-assessed or tested with TM Forum's test kits?
- Which parts of your data sit in vendor-specific extensions?
- Do you support the event notifications, not only the request and response calls?
- Which of your APIs are not TMF-based, and why?
Related Pages
FAQs
Are TM Forum Open APIs free to use?
The specifications are published by TM Forum and widely used across the industry. Check TM Forum's current terms for access to specifications, test kits and formal certification, which may depend on membership.
Do TM Forum APIs replace 3GPP interfaces?
No. 3GPP defines network interfaces, such as those between the core network and charging systems. TM Forum Open APIs cover business and operations systems above the network. A telecom stack uses both.
Is ODA the same as the Open APIs?
No. ODA is the wider reference architecture. It defines standard components and how they fit together, and uses the Open APIs as the interfaces between them.