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 MEC 014 UE Identity API

The UE Identity API from ETSI GS MEC 014, which lets a MEC application register a UE identity tag with the MEC platform so that traffic filtering rules can be applied to a specific device.

ETSI MEC 014 UE Identity API is one of 24 APIs that ETSI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Edge Computing, MEC, and Identity. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 2 operations across 1 path, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 3.1.1.

Requests are made against a single base URL, https://localhost:8081/ui/v1.

2 operations 1 paths 3 schemas 1 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.1.1
Server
https://localhost:8081/ui/v1
Resource Areas
1

Paths & Operations 2

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

uEIdentity 2
GET
/{appInstanceId}/ue_identity_tag_info
Retrieve information about specific UeIdentityTagInfo.
UeidentitytaginfoGETAppinstanceid 2 params → 200400404403
PUT
/{appInstanceId}/ue_identity_tag_info
Register/De-register the information about specific UeIdentityTagInfo.
UeidentitytaginfoPUTAppinstanceid 1 param body → 200400404403412

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are ProblemDetails (5 properties), UeIdentityTags (2 properties), UeIdentityTagInfo (1 property). Each schema is shown below with its type and property counts.

ProblemDetails
object
5 properties
UeIdentityTagInfo
object
1 property 1 required
UeIdentityTags
object
1 to N tags presented by a MEC Application instance to a MEC Platform
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

UEidentityAPI.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 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
ETSI MEC 040 MEC Federation Enablement API
Where this information came from

This is an independent, third-party profile of ETSI MEC 014 UE Identity 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.