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

ETSI OpenSlice TM Forum Open APIs

ETSI SDG OpenSlice is an open-source service-based OSS delivering Network as a Service, and it exposes its catalog, ordering and inventory surface as TM Forum Open APIs. The documentation lists more than twenty exposed endpoints including TMF620 Product Catalog, TMF622 Product Ordering, TMF629 Customer, TMF632 Party, TMF633 Service Catalog, TMF634 Resource Catalog, TMF638 Service Inventory, TMF639 Resource Inventory, TMF640 Service Activation, TMF641 Service Ordering, TMF642 Alarm, TMF651 Agreement, TMF652 Resource Ordering, TMF653 Service Test, TMF657 Service Quality, TMF666 Account, TMF669 Party Role, TMF685 Resource Pool and TMF691 Federated ID. The public OpenSlice demo answers these paths anonymously; ETSI does not hold a TM Forum Open API conformance certification for them.

ETSI OpenSlice TM Forum Open APIs is one of 24 APIs that ETSI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include TM Forum, Open APIs, OSS, BSS, and Service Ordering. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 6 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.0.1, at version 4.0.0.

Requests are made against a single base URL, https://portal.openslice.eu/tmf-api.

6 operations 3 paths 6 schemas 1 DELETE3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
4.0.0
Base URL
https://portal.openslice.eu/tmf-api
Authentication
OAuth 2.0
License
Resource Areas
1

Authentication & Security 1

ETSI OpenSlice TM Forum Open APIs declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (security_auth) using the authorizationCode flow, exposing 2 scopes. By default, every request must be authenticated.

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

lcmRuleSpecification 6
GET
/lcmrulesmanagement/v1/lcmRuleSpecification
List or find LCM RuleSpecification objects
listLCMRuleSpecification 3 params → 500409404403400405200401
POST
/lcmrulesmanagement/v1/lcmRuleSpecification
Creates a LCM RuleSpecification
createLCMRuleSpecification body → 500409403400405401
GET
/lcmrulesmanagement/v1/lcmRuleSpecification/{id}
Retrieves a LCM RuleSpecification by ID
retrieveLCMRuleSpecification 2 params → 500409404403400405200401
DELETE
/lcmrulesmanagement/v1/lcmRuleSpecification/{id}
Deletes a LCM RuleSpecification
deleteLCMRuleSpecification 1 param → 500204409404403400405401
PATCH
/lcmrulesmanagement/v1/lcmRuleSpecification/{id}
Updates partially a LCM RuleSpecification
patchLCMRuleSpecification 1 param body → 500200409404403400405401
GET
/lcmrulesmanagement/v1/lcmRuleSpecification/serviceSpec/{id}
List or find LCM RuleSpecification objects by Service Specification ID
listLCMRuleSpecificationsByServiceSpecID 4 params → 500409404403400405200401

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are LCMRuleSpecification (18 properties), LCMRuleSpecificationUpdate (13 properties), LCMRuleSpecificationCreate (13 properties), ServiceSpecificationRef (9 properties). Each schema is shown below with its type and property counts.

LCMRuleSpecificationCreate
object
The RuleSpecification to be created
13 properties
ServiceSpecificationRef
object
Service specification reference: ServiceSpecification(s) required to realize a ProductSpecification.
9 properties
TargetServiceSchema
object
The reference object to the schema and type of target service which is described by service specification
5 properties
TimePeriod
object
A period of time, either as a deadline (endDateTime only) a startDateTime only, or both
2 properties
LCMRuleSpecification
object
A LCM RuleSpecification is an entity that describes a LCM rule to apply during the LCM of a service.
18 properties
LCMRuleSpecificationUpdate
object
The LCM RuleSpecification to be updated
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

OpenSliceLCMRulesspecificationAPI.json Raw ↑

Other APIs ETSI publishes across the network.

ETSI MEC 011 Edge Platform Application Enablement API
ETSI MEC 012 Radio Network Information API
ETSI MEC 013 Location API
ETSI MEC 014 UE Identity API
ETSI MEC 015 Traffic Management APIs
ETSI MEC 016 UE Application Interface API
ETSI MEC 010-2 Application Package and Lifecycle Management APIs
ETSI MEC 021 Application Mobility Service API
ETSI MEC 028 WLAN Information API
ETSI MEC 029 Fixed Access Information API
ETSI MEC 030 V2X Information Services API
ETSI MEC 033 IoT API
Where this information came from

This is an independent, third-party profile of ETSI OpenSlice TM Forum Open APIs, 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.