This page was moved to https://esci-sd.atlassian.net/wiki/spaces/EWP/overview
Click in the link above if you are not automatically redirected in 10 seconds.


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

Compare with Current View Page History

« Previous Version 20 Next »

If you are using your own in-house built mobility management software, connecting it with the Erasmus Without Paper Network will allow you to communicate with other systems, so that you can send and receive student information as data into your system. Furthermore, you will be able to connect to the Erasmus Mobility Tool+ via connecting to the Erasmus Without Paper Network.

Step-by-step


As a first step it is important to understand the basics (different scenario's for joining EWP, the mobility process cut into pieces) of the EWP infrastructure and apply it to the management of mobility processes at your own institution.

The implementation of EWP will need to be done by your IT team and therefore we encourage you to involve them in the process right from the beginning. They will be responsible for developing the APIs that connect your own system to the system from your partner via the EWP network using the communication protocols.

Your IT team will have two important tasks:

  1. They have to connect your in-house software to the Erasmus Without Paper Network. This is a mainly technical task and there is a lot of documentation available on how to connect. You can redirect them to the EWP developers page  and a special Github repository;
  2. The existing business processes will need to be redesigned once data can be directly exchanged with the partners. This is a task where both the IT-team and the IRO (as business process owners) should be involved (also see step 5).


  1. As a first step some basic APIs should be implemented by your IT team (the so called Primary Network APIs).
  2. As a second step it is important to align the developments with the timeline from the European Commission and the National Agencies. In spring 2021 it was announced that HEIs need to be connected to the EWP Network and to start exchanging Online Learning Agreements and Inter Institutional Agreements with their partners through the EWP network from June 2021. They should be connected at the very latest before the start of the academic year 2022/2023. In order to make sure that no one is left behind, the Commission will consider the 2021/2022 academic year as a transitional year.

The full entry procedure is described in another part of the EWP competence centre. You will have to send a mail to valere.meus(at)uni-foundation.eu to start the process.

The first concrete step is to send the URL of your manifest file.  It will then be entered in the so called development environment so you can start testing. Once the basic APIs have been implemented and tested, you can be added to the production environment and officially accepted as an EWP partner.

Although your IT team will be responsible for connecting your system to EWP, you will need to rethink existing business processes because you will need functionality to send data to your partner institutions or handle data that you receive from your partner. We strongly advise that the IRO as business process owner is directly involved in the rethinking of these processes.

If you have a development/testing environment available, you can identify some partners to test the EWP data exchanges with your partner. An overview of which APIs are supported by your partners can be found in the EWP development registry: https://dev-registry.erasmuswithoutpaper.eu/coverage

You are now ready to start exchanging data with your partners in a digital format.


Entry Process instructions: How can you join EWP?

Technically, we have both a Development  (DEV) and a Production (PROD) environment. There are no conditions to enter the Development environment, but the Production environment is where the real data exchanges take place, so you need to fulfil all conditions to enter it.

You will have to agree to the provisions of the Terms of Use agreement  as an HE Institution and sign it. On our side Joao Bacelar signs it for the EWP consortium as Executive Director of the European University Foundation (EUF), the coordinating institution of the EWP Consortium

You will also have to supply contact details for your institution as soon as you become operational in EWP. We need two names and email addresses from each HEI, one from a policy maker/responsible person who is connected to the student data services used and one on a technical level in case there are operational problems) We will come back to you on this once all the other steps have been taken.

Technically you may find the page for IT people interesting. We have both a developer’s page and a technical GitHub communication channel/repository  (https://github.com/erasmus-without-paper/). We encourage technical people to participate actively there as all code is published there and issues discussed. 


We can also put you on the technical mailing list.

Some Instructional videos for the EWP Network (demonstration):

We also encourage you to consider joining the Open Source University Alliance (OSUA) to contribute to a common repository of university IT systems, allowing you to work in an open format and taking advantage of software modules that have been developed by other Universities.

Since the Network was launched in 2018, all the APIs have been finetuned and now HEIs can connect their student information systems to enable the exchange of information such as:

  • Institutional information
  • Courses
  • Inter-institutional Agreements  (you can also use the Dashboard)
  • Nomination of mobilities 
  • Transcripts of Records
  • Access to Mobility Tool+ data dictionaries 
  • Learning Agreements (you can also use OLA)

Content by label

There is no content with the specified labels



  • No labels