Skip to content
OpenParablePublic APIs

ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API

by etsi.local

No authHTTPSPhone
Open documentation ↗

Overview

ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management described using OpenAPI.

ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management is a phone API from etsi.local. It needs no API key. It is served over HTTPS. Its OpenAPI description documents 16 endpoints.

At a glance

Authentication
No auth
HTTPS
Yes
CORS
Unknown
Category
Phone
Base URL
http://etsi.local
Version
2.1.1
Endpoints
16
OpenAPI
Specification ↗
Spec updated
2021-07-20

Make a first request

Replace the placeholders; the documentation says exactly where credentials go.

cURL
curl -X GET "http://etsi.local/app_packages" \
  -H "Accept: application/json"
JavaScript
const response = await fetch("http://etsi.local/app_packages", {
  method: "GET",
  headers: {
    "Accept": "application/json",
  },
});
const data = await response.json();
console.log(data);
Python
import requests

response = requests.request(
    "GET",
    "http://etsi.local/app_packages",
    headers={
    "Accept": "application/json",
    },
    timeout=30,
)
print(response.json())

Endpoints

MethodPathWhat it does
GET/app_packagesQueries information relating to on-boarded application packages in the MEO
POST/app_packagesCreate a resource for on-boarding an application package to a MEO
GET/app_packages/{appPkgId}Queries the information related to individual application package resources
PATCH/app_packages/{appPkgId}Updates the operational state of an individual application package resource
DELETE/app_packages/{appPkgId}Deletes an individual application package resources
GET/app_packages/{appPkgId}/appdReads the content of the AppD of on-boarded individual application package resources.
GET/app_packages/{appPkgId}/package_contentFetch the onboarded application package content identified by appPkgId or appDId.
PUT/app_packages/{appPkgId}/package_contentUploads the content of application package.
GET/onboarded_app_packages/{appDId}/appdReads the content of the AppD of on-boarded individual application package resources.
GET/onboarded_app_packages/{appDId}/package_contentFetch the onboarded application package content identified by appPkgId or appDId.
PUT/onboarded_app_packages/{appDId}/package_contentUploads the content of application package.
GET/subscriptionsused to retrieve the information of subscriptions to individual application package resource in MEO
POST/subscriptionsSubscribe to notifications about on-boarding an application package
GET/subscriptions/{subscriptionId}Used to represent an individual subscription to notifications about application package changes.
DELETE/subscriptions/{subscriptionId}Deletes the individual subscription to notifications about application package changes in MEO.
POST/user_defined_notificationRegisters a notification endpoint to notify application package operations

Questions

Does the ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API need an API key?

No. The ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API can be called without an API key or sign-up, which makes it handy for prototypes and front-end demos.

Does the ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API support HTTPS?

Yes, the ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API is served over HTTPS.

How many endpoints does the ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API have?

Its OpenAPI description lists 16 endpoints in version 2.1.1. All of them are shown on this page.

What are alternatives to the ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API?

Other Phone APIs include Twilio - Accounts, Twilio - Api, Mobility API, Telnyx API, Twilio - Autopilot.

Compare alternatives →

Twilio - Accounts

Phone

This is the public Twilio REST API.

HTTP Basic13 endpoints

Twilio - Api

Phone

This is the public Twilio REST API.

HTTP Basic199 endpoints

Mobility API

Phone

Transit API can be used to obtain time-aggregated data representing moving the people between various spatial points within the Czech Republic. Having A - 'from' and B - 'to' points, the API can return count of people traveling from A to B or people that are from A and traveling to B, etc. The mobility data is based on moving mobile stations in O2 mobile network.

No auth2 endpoints

Telnyx API

Phone

SIP trunking, SMS, MMS, Call Control and Telephony Data Services.

Bearer token361 endpoints

Twilio - Autopilot

Phone

This is the public Twilio REST API.

HTTP Basic52 endpoints

Socio-demo API

Phone

Socio-demo API can be used to obtain time-aggregated data representing groups of people on the given location in the Czech Republic. Having a location, the API can return count of people belonging to age group or gender aggregated by hours. The socio-demo data is based on presence of mobile stations in O2 mobile network.

No auth3 endpoints

Listed from APIs.guru (CC0).