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 Monitoring Event Subscriptions API

The Monitoring Event Subscriptions API from 3GPP — 1 operation(s) for monitoring event subscriptions.

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

Tagged areas include Monitoring Event Subscriptions. 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 31 schemas. It is described by OpenAPI 3.2.0, at version 1.4.0.

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

2 operations 1 paths 31 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

3GPP Monitoring Event Subscriptions 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.

Monitoring Event Subscriptions 2
GET
/{scsAsId}/subscriptions
Read all or queried active subscriptions for the SCS/AS.
FetchAllMonitoringEventSubscriptions 4 params → 200307308400401403404406
POST
/{scsAsId}/subscriptions
Creates a new subscription resource for monitoring event notification.
CreateMonitoringEventSubscription 1 param body → 201200400401403404411413

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are MonitoringEventSubscription (74 properties), MonitoringEventReport (33 properties), LocationInfo (22 properties), MonitoringNotification (9 properties). Each schema is shown below with its type and property counts.

GroupMembListChanges
object
Represents information on the change(s) to a group's members list.
2 properties
EnergyInfo
object
Contains the Energy consumption information for the UE.
1 property 1 required
LocationFailureCause
Represents the cause of location positioning failure. Possible values are: - POSITIONINGDENIED: Positioning is denied. - UNSUPPORTEDBYUE: Positioning is not su…
AppliedParameterConfiguration
object
Represents the parameter configuration applied in the network.
5 properties
UePerLocationReport
object
Represents the number of UEs found at the indicated location.
4 properties 1 required
PdnConnectionStatus
Represents the PDN connection status. Possible values are - CREATED: The PDN connection is created. - RELEASED: The PDN connection is released. - RATTYPECHANGE…
UeStrAndFwdStatus
Represents the Store and Forward mode status of the UE. Possible values are - INSFMODE: Indicates that the UE is registered in Store and Forward mode. - OUTOFS…
ConsentRevocNotif
object
Represents the user consent revocation information conveyed in a user consent revocation notification.
2 properties 2 required
PdnConnectionInformation
object
Represents the PDN connection information of the UE.
8 properties 2 required
SACRepFormat
Indicates the NSAC reporting format.
UavPolicy
object
Represents the policy information included in the UAV presence monitoring request.
2 properties 2 required
UpLocRepAddrAfRm
objectnull
Represents the user plane addressing information.
3 properties
MonitoringEventSubscription
object
Represents a subscription to event(s) monitoring.
74 properties 2 required
UpCumEvtRep
object
Represents the cumulative event report.
1 property
UeStrAndFwdSatInfo
object
Contains the Store and Forward operation information for satellite access.
5 properties 1 required
LocationType
Represents a location type. Possible values are - CURRENTLOCATION: The SCS/AS requests to be notified for current location - LASTKNOWNLOCATION: The SCS/AS requ…
SubType
Represents a subscription type. Possible values are - AERIALUE: The UE has Aerial subscription.
MonitoringNotification
object
Represents an event monitoring notification.
9 properties 1 required
AssociationType
Represents an IMEI or IMEISV to IMSI association. Possible values are - IMEI: The value shall be used when the change of IMSI-IMEI association shall be detecte…
MonitoringEventReports
object
Represents a set of event monitoring reports.
1 property 1 required
ReachabilityType
Represents a reachability type. Possible values are - SMS: The SCS/AS requests to be notified when the UE becomes reachable for sending SMS to the UE - DATA: T…
MonitoringType
Represents a monitoring event type. Possible values are - LOSSOFCONNECTIVITY: The SCS/AS requests to be notified when the 3GPP network detects that the UE is n…
ApiCapabilityInfo
object
Represents the availability information of supported API.
2 properties 2 required
MonitoringEventReport
object
Represents an event monitoring report.
33 properties 1 required
Accuracy
Represents a desired granularity of accuracy of the requested location information. Possible values are - CGIECGI: The SCS/AS requests to be notified using cel…
ConsentRevoked
object
Represents the information related to a revoked user consent.
3 properties 1 required
LocationInfo
object
Represents the user location information.
22 properties
FailureCause
object
Represents the reason of communication failure.
7 properties
InterfaceIndication
Represents the network entity used for data delivery towards the SCS/AS. Possible values are - EXPOSUREFUNCTION: SCEF is used for the PDN connection towards th…
IdleStatusInfo
object
Represents the information relevant to when the UE transitions into idle mode.
5 properties
PdnType
Represents the PDN connection type. Possible values are - IPV4: PDN connection of IPv4 type. - IPV6: PDN connection of IPv6 type. - IPV4V6: PDN connection of I…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

3gpp-monitoring-event-subscriptions-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 Monitoring Event Subscriptions 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.