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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
ETSI

ETSI MEC 016 UE Application Interface API

The Mx2 reference point from ETSI GS MEC 016, used by a device-side application to discover which MEC applications are available in the system and to request instantiation or termination of a user application in the edge cloud.

Documentation Provider Profile APIs.io OpenAPI GitHub

ETSI MEC 016 UE Application Interface 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 Application Lifecycle. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 5 operations across 4 paths, and defines 22 schemas. It is described by OpenAPI 3.1.0, at version 2.2.1.

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

5 operations 4 paths 22 schemas 1 DELETE1 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.2.1
Server
https://localhost/dev_app/v1
Contact
https://forge.etsi.org/rep/mec/gs016-dev-app-api
License
BSD-3-Clause
Resource Areas
1

Paths & Operations 5

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

dev_app 5
GET
/app_list
Retrieve available application information.
ApplistGET 5 params → 200400401404403
POST
/app_contexts
For requesting the creation of a new application context.
AppcontextsPOST body → 201400401404403
PUT
/app_contexts/{contextId}
For updating the callbackReference and/or appLocation of an existing application context.
AppcontextsPUTContextid 1 param body → 204400401404403
DELETE
/app_contexts/{contextId}
For requesting the deletion of an existing application context.
AppcontextsDELETEContextid 1 param → 204400401404403
POST
/obtain_app_loc_availability
Used to obtain the location constraints for a new application context.
ObtainapplocavailabilityPOST body → 200400401404403

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are AppInfo (8 properties), AppInfo1 (8 properties), AppInfo2 (7 properties), AppContext (6 properties). Each schema is shown below with its type and property counts.

ProblemDetails
object
5 properties
Polygon
object
1 property
InlineNotification
ApplicationList
object
|- NOTE 1: The vendor specific extension allows submitting information on the application lists that have been made available to the device application of the…
1 property
AppContext
object
6 properties 2 required
ApplicationLocationAvailability
object
2 properties 2 required
AddressChangeNotification
object
4 properties 4 required
ApplicationContextDeleteNotification
object
2 properties 2 required
ApplicationContextUpdateNotification
object
3 properties 3 required
ApplicationLocationAvailabilityNotification
object
3 properties 2 required
LocationConstraints
object
3 properties
AppCharcs
object
Characteristics of the application. As defined below. The application characteristics relate to the system resources consumed by the application. A device appl…
5 properties
AppInfo
object
8 properties 6 required
VendorSpecificExt
object
Extension for vendor specific information (see note 1).
1 property 1 required
AppList
object
List of user applications available to the device application. As defined below.
2 properties 1 required
UserAppInstanceInfo
object
List of user application instance information.
3 properties
AppInfo1
object
8 properties 4 required
AvailableLocations
object
MEC application location constraints.
1 property
AppInfo2
object
7 properties 3 required
UserAppInstanceInfo1
object
List of user application instance information.
3 properties 2 required
AvailableLocations1
object
Locations available to the MEC application.
1 property 1 required
CivicAddressElement
object
Zero or more elements comprising the civic address. Shall be absent if the "area" attribute is present.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

UEAppInterfaceApi.yaml Raw ↑

Other APIs ETSI publishes across the network.

ETSI MEC 011 Edge Platform Application Enablement API
AE Profile APIs.io
ETSI MEC 012 Radio Network Information API
AE Profile APIs.io
ETSI MEC 013 Location API
AE Profile APIs.io
ETSI MEC 014 UE Identity API
AE Profile APIs.io
ETSI MEC 015 Traffic Management APIs
AE Profile APIs.io
ETSI MEC 010-2 Application Package and Lifecycle Management APIs
AE Profile APIs.io
ETSI MEC 021 Application Mobility Service API
AE Profile APIs.io
ETSI MEC 028 WLAN Information API
AE Profile APIs.io
ETSI MEC 029 Fixed Access Information API
AE Profile APIs.io
ETSI MEC 030 V2X Information Services API
AE Profile APIs.io
ETSI MEC 033 IoT API
AE Profile APIs.io
ETSI MEC 040 MEC Federation Enablement API
AE Profile APIs.io
#Edge Computing#MEC#Application Lifecycle
← Back to E APIs
API Details
ID
etsi:mec-016-ue-application-interface
Server
https://localhost/dev_app/v1
Docs
https://forge.etsi.org/rep/mec/gs016-dev-app-api
Provider
ETSI
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=mec-016-ue-application-interface&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mec-016-ue-application-interface"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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