TELECOMMUNICATIONS

Telecom API management.
From TM Forum Open APIs to partner portals.

At most operators, product catalog, ordering, inventory, and network APIs are spread across many systems and versions. API Portal brings their specs into one catalog and gives each partner exactly the APIs they need.

v4 + v5
TMF specs side by side
EU
Hosted in Frankfurt
SSO
Okta, Azure AD, Keycloak
app.api-portal.io/telco
Telco TM Forum CAMARA
TMF620 v5
Product Catalog
TMF622 v4
Product Ordering
TMF638 Wholesale
Service Inventory
CAMARA
SIM Swap
Ready for specs from these standards
TM Forum Open APIs CAMARA OpenAPI 3.x Swagger 2.0 AsyncAPI

// The Challenge

Why telecom operators need an
API Portal.

An operator's business IT is rarely built in one piece. CRM, ordering, inventory, and network come from different vendors, and every API has its own consumers inside the company and at partners.

TMF APIs in v4 and v5 at once

The ordering system speaks TMF622 v4, the new product catalog already runs TMF620 v5, and both carry their own extensions. Usually only the team that runs an API knows which version is live where.

Wholesale partners without self-service

Resellers, MVNOs, and wholesale customers order through ordering and qualification APIs. The documentation often goes out as a PDF, and every new version triggers another round of questions.

Network APIs for external developers

CAMARA and GSMA Open Gateway bring in consumers who don't know the network. They need a spec they can try in the browser and a clear path to access.

// Use Cases

Built for
operators and telco platforms.

TM Forum Open APIs

Bring TM Forum Open APIs into one catalog.

TM Forum publishes its Open APIs as spec files, with version 4 in Swagger 2.0 and version 5 in OpenAPI 3.0. The catalog accepts both formats, so TMF620, TMF622, or TMF641 sit next to your own APIs, extensions included. Teams can see at a glance which system offers which version.

  • Swagger 2.0 and OpenAPI 3.x in the same catalog
  • Version diff between v4 and v5
  • House rules and TMF630 guidelines as custom linter rules
See the API Catalog →
app.api-portal.io/telco/tmf620/diff
v4.1.0 · Swagger 2.0 → v5.0.0 · OpenAPI 3.0
GET/productOffering
GET/catalogBreaking
GET/productCatalogv5
GET/productOfferingPrice/{id}
POST/importJob
Partners & Wholesale

Partner portals for wholesale, resellers, and MVNOs.

Each partner group gets its own portal with its ordering, qualification, and inventory APIs. Business groups and roles control who sees which spec, and new versions show up there with a changelog.

  • A dedicated portal per partner group
  • Access by business group and role
  • White label with a custom domain
See Enterprise Portals →
wholesale.telco-partner.example
TMF645
Service Qualification
TMF622
Product Ordering
TMF638
Service Inventory
AsyncAPI
Order Events
Network APIs

Make CAMARA network APIs easy to adopt.

CAMARA defines network APIs such as SIM Swap, Number Verification, and Quality on Demand as OpenAPI specs, and operators in GSMA Open Gateway offer them in a consistent way. In the portal, you can document these specs, try them in the explorer, and version them per meta-release.

  • Try it out in the API Explorer
  • Versions per CAMARA meta-release
  • Separate views for internal teams and external developers
See the API Explorer →
app.api-portal.io/telco/network-apis
POST/checkSIM Swap
POST/retrieve-dateSIM Swap
POST/verifyNumber Verification
POST/sessionsQuality on Demand
GET/sessions/{sessionId}Quality on Demand

// Security & Operations

Ready for
critical infrastructure.

Telecom networks are critical infrastructure, and NIS2 sets high expectations for the systems behind them. The portal provides building blocks that can feed into your security concepts.

Role-based access

Roles, business groups, and environment policies define who can see and change which API. Sign-in runs through SSO with Okta, Azure AD, or Keycloak.

Audit logs for every change

The audit log records who changed which spec and when. That gives internal reviews and external audits a traceable record.

On-premises option

On the Enterprise plan, the platform can also run in your own infrastructure.

Hosted in Frankfurt

The cloud version runs in EU data centers in Frankfurt, and your data stays in the EU.

// API Landscape

Typical telecom APIs
managed in the portal.

The examples range from product catalog and ordering to network APIs. The paths come from the published TM Forum and CAMARA specs.

REST TMF620 v5

Product Catalog Management

Product offerings, prices, and categories shared by CRM, web shop, and partner channels.

GET /productOffering
GET /productOfferingPrice/{id}
REST TMF622 v5

Product Ordering

Orders from end customers and partners, with order items, status, and cancellation.

POST /productOrder
POST /cancelProductOrder
REST TMF645 v5

Service Qualification

Checks before ordering whether a service is available at an address or access line.

POST /checkServiceQualification
GET /checkServiceQualification/{id}
Swagger 2.0 TMF641 v4.2

Service Ordering

Technical orders to the network, such as activating or changing a service.

POST /serviceOrder
GET /serviceOrder/{id}
REST CAMARA

SIM Swap

Reports whether and when the SIM card for a phone number was last swapped, for example to prevent fraud.

POST /check
POST /retrieve-date
REST CAMARA

Quality on Demand

Requests a specific network quality for a session and checks its status.

POST /sessions
GET /sessions/{sessionId}

// Architecture

Fits into your OSS/BSS landscape.

In an ODA architecture, every component exposes its functions through Open APIs, and legacy systems usually keep their specs in their own repositories. With the CLI and CI/CD, these specs reach the portal on every release, and nobody has to upload them by hand.

  • CI/CD with GitHub Actions, GitLab CI, and Jenkins
  • CLI and REST API for automation
  • AsyncAPI for event and notification APIs
  • SSO via SAML with your corporate directory
  • On-premises on the Enterprise plan
gitlab-ci.yml

# .gitlab-ci.yml · Telco API Portal Sync

stages:

  - validate

  - deploy

validate-specs:

  stage: validate

  script:

    - apiportal lint ./specs/tmf/*.yaml

    - apiportal lint ./specs/camara/*.yaml

deploy-portal:

  stage: deploy

  script:

    - apiportal deploy --env prod

  only:

    - main

// FAQ

Common questions from telecom teams.

Still have questions? Our team is happy to help.

Contact Sales
Yes. TM Forum publishes version 4 of its Open APIs in Swagger 2.0 and version 5 in OpenAPI 3.0, and the catalog accepts both formats. Each version is tracked separately, and the version diff shows which fields and endpoints changed between two releases. Your own extensions stay part of the respective spec.
Roles and business groups let you decide which APIs a partner can see. With Enterprise Portals, each partner group also gets its own portal, with your branding and a custom domain if you want them. You invite new partners by email and assign their role and business group right away.
Yes. CAMARA describes its APIs as OpenAPI 3.0 specs, which you can add to the catalog and try in the API Explorer like any other spec. Consent, authentication, and billing still run through the operator's network and gateway.
No. The gateway receives the calls and enforces limits and authentication. The portal manages the specs, the documentation, and access to them, so internal teams and partners can find and understand the right API. In practice, the two work side by side.
The portal provides building blocks that operators need for their NIS2 security concepts. These include roles and permissions per API, SSO, audit logs for every change, and hosting in the EU. How these blocks fit into your own concept, and what you need to document, is for you as the operator to assess.
Yes, on the Enterprise plan the platform can run in your own infrastructure. The best way to find the right setup is a conversation about your environment.

Let's talk about your telecom APIs.

In a demo, we show how catalog, versioning, and partner portals work together with TMF specs.