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 040 MEC Federation Enablement API

The MEC Federation enablement API from ETSI GS MEC 040, which lets edge systems operated by different providers discover one another, exchange availability zone and system information, and federate so an application can run across operator boundaries.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 5 operations across 2 paths, and defines 11 schemas. It is described by OpenAPI 3.1.0, at version 3.1.1.

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

5 operations 2 paths 11 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.1.1
Server
https://localhost/fed_enablement/v1
Contact
https://forge.etsi.org/rep/mec/gs040-fed-enablement-api
License
BSD-3-Clause
Resource Areas
1

Paths & Operations 5

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

systemInfo 5
GET
/fed_resources/system_info
Retrieve a list of systeminfo resources (see clause 6 for data model) of federation members.
FedresourcesSysteminfoGET 3 params → 200400401403404
POST
/fed_resources/system_info
Create new systeminfo resource for a given MEC system.
FedresourcesSysteminfoPOST body → 201400401403404
GET
/fed_resources/system_info/{systemId}
Retrieve the systeminfo resource of the federation member with systemId as its system identifier.
FedresourcesSysteminfoGETSystemid 1 param → 200400401403404
PATCH
/fed_resources/system_info/{systemId}
Update the systeminfo resource for a given MEC system.
FedresourcesSysteminfoPATCHSystemid 1 param body → 200400401403404
DELETE
/fed_resources/system_info/{systemId}
Delete the systeminfo resource for a given MEC system.
FedresourcesSysteminfoDELETESystemid 1 param → 204400401403404

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are ProblemDetails (5 properties), SystemUpdateNotificationSubscription (5 properties), EndPointInfo (4 properties), SystemInfo (3 properties). Each schema is shown below with its type and property counts.

ProblemDetails
object
5 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
LinkType
object
1 property 1 required
EndPointInfo
object
|- NOTE: Exactly one of "uris", "fqdn", "addresses" or "alternative" shall be present.
4 properties
SystemInfo
object
3 properties 3 required
SystemInfoUpdate
object
|- NOTE: At least one attribute shall exist.
2 properties
SystemUpdateNotificationSubscription
object
5 properties 2 required
SystemUpdateNotification
object
3 properties 3 required
TimeStamp
object
2 properties 2 required
_links
object
Object containing hyperlinks related to the resource. This shall only be included in the HTTP responses.
1 property 1 required
_links1
object
Object containing hyperlinks related to the resource.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

MEC040_fedEnablement.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 033 IoT API
AE Profile APIs.io
#Edge Computing#MEC#Federation
← Back to E APIs
API Details
ID
etsi:mec-040-federation-enablement
Server
https://localhost/fed_enablement/v1
Docs
https://forge.etsi.org/rep/mec/gs040-fed-enablement-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-040-federation-enablement&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mec-040-federation-enablement"

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 040 MEC Federation Enablement 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.