Lagrama to OGC-ST translator: This API allows to translate a proprietary data model in the Lagrama spec to the OGC-ST standard ⚠️ Insecure (not HTTPS) API spec URL: http://efpf.polito.it:8878/openapi.json
NiFi REST API: HTTP/REST API of Data Spine NiFi, to be used mostly for automation and integration testing. ❌ No URL or schema for API spec
Data Spine Service Registry: Data Spine’s Service Registry for lifecycle management (CRUD, list operations) and discovery/filtering of synchronous and asynchronous services in the EFPF ecosystem
Service Registry’s MQTT Service Registration/Deregistration API: Lifecycle management of services using MQTT: Service Registry (SR) also supports MQTT for service registration, updates and de-registration. Service registration/update is similar to PUT method of REST API. Here, a service uses a pre-configured topic defined in the config file (see commonRegTopics and regTopics) for publishing the message. The will message of the registered service is used to de-register it from the SR. The will topics are also defined in the config file (see commonWillTopics and willTopics).
Service Registry’s MQTT Service Status Announcement API: Service registration status announcements over MQTT: Service Registry announces the service registration and updates via MQTT using retain messages. Service Registry also announces the service de-registration (on explicit de-registration request via REST/MQTT API or on expiration due to the set TTL) via MQTT.
EFPF Accountancy Service: The Accountancy Service is an integral part of the EFPF Marketplace Framework and provides insight into users’ interactions with the EFPF Platform as well as its connected marketplaces. This includes transactions that EFPF users make on different marketplaces, which are linked with the EFPF Marketplace Framework.
Logstash endpoint for data ingestion and pipeline: Accountancy Service uses Logstash as a data ingestion and server-side data processing pipeline. The logs sent to Logstash are forwarded to Elasticsearch for persistence after executing certain ingestion pipelines. ❌ No URL or schema for API spec