Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Welcome to the ONF Transport API project !

The ONF Transport API (TAPI) project charted under the ONF Open Transport Configuration & Control (OTCC) is responsible for the development of this SDK as an Open Source project. The TAPI SDK supports interfaces to the following functional modules:

  • Topology Service
  • Connectivity Service
  • OAM Service
  • Equipment Inventory
  • Virtual Network Service
  • Path Computation Service
  • Streaming Service
  • Notification Service

For further information, please read the TAPI Overview.

If you would like to dive a bit deeper, TAPI v2.4.0 Reference Implementation Agreement (TR-547 v2.0) - December 2022 is a good start and TAPI v2.4.0 Reference Implementation Agreement-Streaming (TR-548 v2.0) - December 2022 provides more information on TAPI Streaming.

The SDK is hosted on ONF Github repository at

Latest Release:

For the new features introduced by version 2.4.0 see ONF releases Transport API (TAPI) v2.4.0 to further advance SDN Control and OSS integration

The plan: TAPI Roadmap 2022-2023

The SDK is released under the Apache 2.0 license and consists of following components:

  • TAPI UML Information Model - which is pruned/refactored from the ONF Core Information Model 1.2 (the latest version is v1.5 is best understood through TR-512_v1.5_OnfCoreIm).
  • TAPI YANG Schema - which is generated using the EAGLE UML-to-YANG mapping tool
  • TAPI SWAGGER definitions - which is generated using the EAGLE YANG-to-JSON tool
  • TAPI Reference Implementation - the code stubs for which are generated using the swagger-code for python
  • TAPI Development Guide - a PDF document providing an overview of the SDK.
The project uses the following mailing/discussion list:!forum/transport-api