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 033 IoT API

The IoT API from ETSI GS MEC 033, defining how IoT device registration, IoT platform selection and device-to-platform association are managed by a MEC system so that IoT traffic can be terminated and processed at the edge.

Documentation Provider Profile APIs.io OpenAPI GitHub

ETSI MEC 033 IoT 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 IoT. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 10 operations across 4 paths, organized into 2 resource areas, and defines 21 schemas. It is described by OpenAPI 3.1.0, at version 3.1.1.

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

10 operations 4 paths 21 schemas 2 DELETE4 GET2 POST2 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/amsi/v1
Contact
ETSI Forge
License
BSD-3-Clause
Resource Areas
2

Paths & Operations 10

Across 4 paths, the API surfaces 10 operations — 2 DELETE, 4 GET, 2 POST, 2 PUT. They span 2 resource areas: reg-dev, reg-iot-plat. Each is listed below with its method, path, parameters, and response codes.

reg-dev 5

registereddevices

GET
/registered_devices
Retrieve information about all devices with a valid traffic rule association - see clause 5.2.2.
registereddevicesGET 2 params → 200400404403
POST
/registered_devices
Register a new device - see clause 5.2.3.
registereddevicesPOST body → 201400404403
GET
/registered_devices/{registeredDeviceId}
Retrieve information about a device - see clause 5.2.4.
registereddevicesByIdGET 1 param → 200400404403
PUT
/registered_devices/{registeredDeviceId}
Update information about a device including its association to a valid traffic rule - see clauses 5.2.5 and 5.4.3.
registereddevicesByIdPUT 1 param body → 200400404403412
DELETE
/registered_devices/{registeredDeviceId}
Deregister a device - see clause 5.2.6.
registereddevicesByIdDELETE 1 param → 204404403
reg-iot-plat 5

registerediotplatforms

GET
/registered_iot_platforms
Retrieve information about all IoT platforms - see clause 5.3.2.
registerediotplatformsGET 1 param → 200400404403
POST
/registered_iot_platforms
Register a IoT platform - see clause 5.3.4.
registerediotplatformsPOST body → 201400404403
GET
/registered_iot_platforms/{registeredIotPlatformId}
Discover native services and obtain information about user transports provided by a IoT platform - see clauses 5.3.3 and 5.4.2.
registerediotplatformsByIdGET 2 params → 200400404403
PUT
/registered_iot_platforms/{registeredIotPlatformId}
Update information about a IoT platform - see clause 5.3.5.
registerediotplatformsByIdPUT 1 param body → 200400404403412
DELETE
/registered_iot_platforms/{registeredIotPlatformId}
Deregister a IoT platform - see clause 5.3.6.
registerediotplatformsByIdDELETE 1 param → 204404403

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are DeviceInfo (17 properties), TrafficFilter (15 properties), UplinkMsg (11 properties), EventMsg (10 properties). Each schema is shown below with its type and property counts.

ProblemDetails
object
5 properties
DeviceInfo
object
NOTE 1: At least one attribute among gpsi, pei, supi, msisdn, imei, imsi, and iccid should be provided. Sufficient security measures shall be put in place when…
17 properties 3 required
IotPlatformInfo
object
4 properties 3 required
MBTransportInfo
object
9 properties 8 required
EventMsg
object
10 properties 2 required
UplinkMsg
object
11 properties 2 required
DeviceSpecificMessageFormats
object
Format of the messages to be published by the MEC IoTS on the user transport provided by the associated IoT platform in case the MEC IoTS acts on behalf of the…
2 properties
DownlinkInfo
object
Downlink communication configuration of the user transport provided by the associated IoT platform in case the MEC IoTS acts on behalf of the IoT device.
2 properties
ImplSpecificInfo
object
Additional implementation specific details of the transport.
3 properties
SerializerType
string
The enumeration SerializerType represents types of serializers.
TransportInfo
object
9 properties 7 required
TransportType
string
Enumeration representing types of transports.
EndPointInfo
object
NOTE: Exactly one of "uris", "fqdn", "addresses" or "alternative" shall be present.
4 properties
SecurityInfo
object
2 properties
Addresses
object
Entry point information of the service as one or more pairs of IP address and port. See note.
2 properties 2 required
OAuth2Info
object
Parameters related to use of OAuth 2.0. Shall be present in case OAuth 2.0 (see IETF RFC 6749 [13]) is supported to secure the provision of the service over th…
2 properties 1 required
TrafficRuleDescriptor
object
NOTE 1: Value indicates the priority in descending order, i.e. with 0 as the highest priority and 255 as the lowest priority. NOTE 2: Some applications (like i…
6 properties 5 required
TrafficFilter
object
15 properties
InterfaceDescriptor
object
5 properties 1 required
TunnelInfo
object
4 properties 3 required
KeyValuePair
object
Key-value pairs for device metadata
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

MEC033_IoT.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 016 UE Application Interface API
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 040 MEC Federation Enablement API
AE Profile APIs.io
#Edge Computing#MEC#IoT
← Back to E APIs
API Details
ID
etsi:mec-033-iot
Server
https://localhost/amsi/v1
Docs
https://forge.etsi.org/rep/mec/gs033-iot-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-033-iot&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mec-033-iot"

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 033 IoT 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.