Skip to content

Layer 3

Open APIs and TM Forum conformance

Business and service capability exposed to ISPs and RSPs, end customers, construction companies, partners and third-party ecosystems through conformant, TMF-numbered interfaces.

The point

Integration as configuration, not a project

When both sides implement the same TM Forum contract, onboarding a retail partner becomes a configuration exercise: credentials, scopes, catalogue mapping and test cases. That is the difference between a two-week onboarding and a two-quarter one.

Blue domain

Commerce

Lets partners and customers check availability, view products and place orders.

Commerce APIs and TM Forum references
APITM Forum reference
Service QualificationTMF679
Product CatalogueTMF620
Product OfferingTMF622
Service OrderingTMF641
Shopping CartTMF654
Customer ManagementTMF629
Party ManagementTMF632

Green domain

Service Management

Supports the full service lifecycle from order to active service.

Service Management APIs and TM Forum references
APITM Forum reference
Service ActivationTMF640
Service ModificationTMF645
Service TerminationTMF646
Service EligibilityTMF678
Service ConfigurationTMF640
Service FeasibilityTMF679
Appointment ManagementTMF673

Red domain

Assurance

Real-time service and network status, fault handling and performance reporting.

Assurance APIs and TM Forum references
APITM Forum reference
Service StatusTMF639
Trouble TicketTMF637
Problem ManagementTMF638
Alarm ManagementTMF656
Event ManagementTMF688
Service MonitoringTMF661
SLA ManagementTMF662

Purple domain

Field Service

Scheduling, dispatch and tracking of field activities.

Field Service APIs and TM Forum references
APITM Forum reference
Appointment ManagementTMF673
Work Order ManagementTMF641
Workforce ManagementTMF Workforce IG1224
DispatchTMF641
Work StatusTMF642
Resource AvailabilityTMF689
Work CompletionTMF641

Amber domain

Data / Reporting

Network and service data for operational and commercial reporting.

Data / Reporting APIs and TM Forum references
APITM Forum reference
Inventory ManagementTMF663
Resource InventoryTMF699
Geographic Address ManagementTMF673
Serviceable AddressTMF671
Usage / MeteringTMF659
Billing AccountTMF678
Billing EventTMF660
Performance ManagementTMF739
KPI ReportingTMF657

Gateway and security

API Gateway and Integration Layer

Every external interface enters through one gateway, so security, quotas and observability are consistent rather than per-integration.

Identity and access

OAuth2 client credentials and authorisation code flows, scoped per partner and per API domain.

Transport security

HTTPS everywhere, with mTLS available for system-to-system partners.

Throttling and quotas

Per-consumer rate limits and quotas enforced at the gateway rather than in application code.

Monitoring

Request, latency and error telemetry per consumer, with alerting on SLA-affecting degradation.

Event streaming

Domain events published to subscribers, so partners react to state change rather than polling.

Webhooks

Registered callbacks with retry and signature verification for order, appointment and fault events.

Conformance

What conformance does and does not mean

Conformant interfaces remove the argument about payload shape. They do not remove the need to agree catalogue, SLA and process — so onboarding is scoped around those instead.

Handled by the standard

  • Resource models, state machines and error semantics
  • Qualification, ordering, activation and ticket lifecycles
  • Event and notification structures
  • Versioning expectations between parties

Still yours to agree

  • Product catalogue and commercial terms
  • SLA definitions and remedy
  • Appointment rules and field responsibilities
  • Settlement periods and dispute process

See the platform against your own operation

A demo walks the architecture, the modules you would actually use and the TM Forum interfaces your partners would integrate against. Bring your operating model and we will map it.