You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Working group on APIs and Blockchain

The Informal Cooperation Network for eDelivery showed interest in exploring future developments that could be added into the eDelivery framework by leveraging on API and Blockchain related initiatives already in place across the Member States.

This page aims to collect use cases for REST-based API extensions for eDelivery that could serve as a basis to understand the possible upcoming developments to be undertaken by CEF eDelivery.

All members of the Informal Cooperation Network for eDelivery and Subgroup on future of eDelivery are invited to participate and provide their input by  

How can I contribute?

You can edit the page directly to add your use case(s) in the table below.

In case you are not able to edit the page, you can also write on the comments' box at the bottom of the page with the relevant information about your use case(s).

Please make sure to contribute by .

Background information

About the ISA² action on Innovative Public Services (future of CEF eDelivery):


For 2020, this action has, among others, the objective of developing relevant legal, organisational and technical artefacts trialled through an extension and combination of the CEF eDelivery building block with blockchain based transactions’ log and a REST-based profile (a.k.a. APIs approach), that support new patterns of data access by request and data sharing.


The work related to the REST-based profile will take as input the JRC study on APIs4DGov that analysed the API technological landscape and  its standards and technical specifications for general purpose use. This aims to support the definition of stable APIs for digital government services, avoiding the need to develop ad-hoc solutions and helping stakeholders in the identification and selection of such solutions.


The scope of the ISA² action will be to develop the following:

  • A set of guidelines and specifications for establishing interoperable REST-based APIs for service invocation and publication of both open and protected data. Sample library implementation for API’s as well as software supporting central/core services such as service catalogues and service discovery could be also in scope.
  • Extension of eDelivery with other building blocks and innovative technical approaches such as blockchain and APIs. Should the pilots be successful, the CEF eDelivery building block will be enriched with a REST-based profile and a blockchain-based log of transactions. Every element will be modular so that it can be used in combination with the existing AS4-profile (of eDelivery) or on its own.

Use cases 

Please provide input on possible use cases for REST-based API extensions for eDelivery.


Title of UCDescriptionActorsPurpose of communicationMessage Exchange PatternParty identification

Non-repudiation

Applicable limitation(s) of eDelivery AS4 profile

Synchronous or asynchronous communication?

Critical features required

Contact pointDiscussion
UC 1











UC 2











UC 3











UC 4











UC 5











  • No labels