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 CAMARA-as-a-Service QoD Provisioning API

A CAMARA Quality on Demand (QoD) Provisioning API implementation shipped as an add-on to ETSI OpenSlice. It wraps a running TM Forum service inventory entry so an operator can expose an existing 5G core or network slice through a standard CAMARA endpoint: set, retrieve and delete a device QoS profile. Security is declared as OpenID Connect, matching the CAMARA authorisation model; no CIBA grant is declared in this document.

ETSI OpenSlice CAMARA-as-a-Service QoD Provisioning API is one of 24 APIs that ETSI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include CAMARA, Quality on Demand, Network APIs, 5G, and Network Slicing. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 4 operations across 3 paths, and defines 24 schemas. It is described by OpenAPI 3.0.3, at version 0.1.0.

Requests are made against a single base URL, {apiRoot}/qod-provisioning/v0.1.

4 operations 3 paths 24 schemas 1 DELETE1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0.1.0
Server
{apiRoot}/qod-provisioning/v0.1
Authentication
OpenID Connect, HTTP Bearer
License
Resource Areas
1

Authentication & Security 2

ETSI OpenSlice CAMARA-as-a-Service QoD Provisioning API declares 2 security schemes for authenticating requests. It supports OpenID Connect (openId) discovered at https://example.com/.well-known/openid-configuration. It accepts HTTP bearer tokens ({$request.body#/sinkCredential.credentialType}) (notificationsBearerAuth).

  • openId — OpenID Connect authentication
  • notificationsBearerAuth — Bearer authentication for notifications

Paths & Operations 4

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

QoD Provisioning 4

Manage the permanent provisioning of QoD

POST
/device-qos
Sets a new provisioning of QoS for a device
createProvisioning 1 param body → 201400401403404409422429
DELETE
/device-qos/{provisioningId}
Deletes a QoD provisioning
deleteProvisioning 2 params → 204202400401403404429500
GET
/device-qos/{provisioningId}
Get QoD provisioning information
getProvisioningById 2 params → 200400401403404429500503
POST
/retrieve-device-qos
Gets the QoD provisioning for a device
retrieveProvisioningByDevice 1 param body → 200400401403404422429500

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are CloudEvent (7 properties), Device (4 properties), BaseProvisioningInfo (4 properties), EventStatusChanged_allOf_data (3 properties). Each schema is shown below with its type and property counts.

ProvisioningId
string
Provisioning Identifier in UUID format
BaseProvisioningInfo
object
Common attributes of a QoD provisioning
4 properties 1 required
ProvisioningInfo
Provisioning related information returned in responses. Optional device object only to be returned if provided in createProvisioning. If more than one type of…
CreateProvisioning
Attributes to request a new QoD provisioning
RetrieveProvisioningByDevice
object
Attributes to look for QoD provisioning
1 property
SinkCredential
object
A sink credential provides authentication or authorization information necessary to enable delivery of events to a target.
1 property 1 required
PlainCredential
object
A plain credential as a combination of an identifier and a secret.
AccessTokenCredential
object
An access token credential.
RefreshTokenCredential
object
An access token credential with a refresh token.
5 required
Port
integer
TCP or UDP port number
QosProfileName
string
A unique name for identifying a specific QoS profile. This may follow different formats depending on the service providers implementation. Some options address…
CloudEvent
object
Event compliant with the CloudEvents specification
7 properties 5 required
EventStatusChanged
Event to notify a QoD provisioning status change
StatusInfo
string
Reason for the new status: NETWORKTERMINATED - Network terminated the QoD provisioning DELETEREQUESTED- User requested the deletion of the QoD provisioning
Device
object
End-user equipment able to connect to the network. Examples of devices include smartphones or IoT sensors/actuators. The developer can choose to provide the be…
4 properties
NetworkAccessIdentifier
string
A public identifier addressing a subscription in a mobile network. In 3GPP terminology, it corresponds to the GPSI formatted with the External Identifier ({Loc…
PhoneNumber
string
A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Num…
DeviceIpv4Addr
object
The device should be identified by either the public (observed) IP address and port as seen by the application server, or the private (local) and any public (o…
3 properties
SingleIpv4Addr
string
A single IPv4 address with no subnet mask
DeviceIpv6Address
string
The device should be identified by the observed IPv6 address, or by any single IPv6 address from within the subnet allocated to the device (e.g. adding ::0 to…
Status
string
The current status of the requested QoD provisioning. The status can be one of the following: REQUESTED - QoD provisioning has been requested but is still bein…
StatusChanged
string
The current status of a requested or previously available QoD provisioning. Applicable values in the event are: AVAILABLE - The requested QoS profile has been…
ErrorInfo
object
Common schema for errors
3 properties 3 required
EventStatusChanged_allOf_data
object
Event details depending on the event type
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openslice-camara-qod-provisioning.yaml 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 CAMARA-as-a-Service QoD Provisioning API, 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.