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

3GPP NIDD configurations API

The NIDD configurations API from 3GPP — 1 operation(s) for nidd configurations.

3GPP NIDD configurations API is one of 194 APIs that 3GPP publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include NIDD configurations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 1 path, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 1.3.0.

Requests are made against a single base URL, {apiRoot}/3gpp-nidd/v1.

2 operations 1 paths 15 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.3.0
Base URL
{notificationRecipientAddress}
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

3GPP NIDD configurations API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oAuth2ClientCredentials) using the clientCredentials flow. By default, every request must be authenticated, though some operations may also be called without credentials.

Paths & Operations 2

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

NIDD configurations 2
GET
/{scsAsId}/configurations
Read all NIDD configuration resources for a given SCS/AS.
FetchAllNIDDConfigurations 1 param → 200307308400401403404406
POST
/{scsAsId}/configurations
Create a new NIDD configuration resource.
CreateNIDDConfiguration 1 param body → 201400401403404411413415

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are NiddConfiguration (16 properties), NiddDownlinkDataTransfer (12 properties), ManagePort (6 properties), NiddConfigurationStatusNotification (6 properties). Each schema is shown below with its type and property counts.

NiddConfigurationStatusNotification
object
Represents an NIDD configuration status notification.
6 properties 2 required
NiddDownlinkDataTransfer
object
Represents the received NIDD downlink data from the SCS/AS.
12 properties 1 required
NiddConfiguration
object
Represents the configuration for NIDD.
16 properties 1 required
DeliveryStatus
Represents the status of a downlink NIDD data delivery resource. Possible values are: - SUCCESS: Success but details not provided - SUCCESSNEXTHOPACKNOWLEDGED:…
NiddStatus
Represents the status of a NIDD configuration. Possible values are: - ACTIVE: The NIDD configuration is active. - TERMINATEDUENOTAUTHORIZED: The NIDD configura…
ManageEntity
Represents the origin that manages the RDS port. Possible values are: - UE: Representing the UE. - AS: Representing the Application Server.
NiddDownlinkDataDeliveryStatusNotification
object
Represents the delivery status of a specific NIDD downlink data delivery.
3 properties 2 required
PdnEstablishmentOptions
Represents PDN establishment options that describe the network behaviour when there is no PDN connection towards the addressed UE. Possible values are: - WAITF…
GmdNiddDownlinkDataDeliveryNotification
object
Represents the delivery status of a specific group NIDD downlink data delivery.
2 properties 2 required
ManagePort
object
Represents the configuration of a RDS dynamic port management.
6 properties 1 required
NiddUplinkDataNotification
object
Represents NIDD uplink data to be notified to the SCS/AS.
6 properties 2 required
SerializationFormat
Represents a serialization format associated with an RDS port which is applicable for the Rdsserializationformat feature. Possible values are - CBOR: The CBOR…
RdsPort
object
Represents the port configuration for Reliable Data Transfer.
2 properties 2 required
GmdResult
object
Represents the group message delivery result.
4 properties 1 required
ManagePortNotification
object
Represents a ManagePort notification of port numbers that are reserved.
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

3gpp-nidd-configurations-api-openapi.yml Raw ↑

Other APIs 3GPP publishes across the network.

3GPP Forge API
3GPP 3gpp Nidd Configuration Trigger API
3GPP 5GLAN Parameters Provision Subscriptions API
3GPP Access Control Policy List (Collection) API
3GPP ACS Configuration Subscriptions API
3GPP Activation Management API
3GPP Addressing Parameters Provisionings (Collection) API
3GPP AF level UE location update notification operation API
3GPP AIoT Command Request (custom operation without associated resources) API
3GPP AIoT Inventory Request (custom operation without associated resources) API
3GPP All API Provider Domains Registrations (Collection) API
3GPP All published service APIs (Collection) API
Where this information came from

This is an independent, third-party profile of 3GPP NIDD configurations 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.