In-house software

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 1: get familiar with the EWP basics

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.

 Step 2: identify IT stakeholders in 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 of your partner via the EWP network using the communication protocols.

 Step 3: redirect the IT team to technical documentation

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).
 Step 4: support the IT team in setting priorities
  1. As a first step some basic APIs should be implemented by your IT team (the so-called Primary Network APIs: Echo, Institutions, Organizational Units).
  2. As a second step it is important to align the developments with the targets from the European Commission and the National Agencies. Contact your National Agency for more information.
 Step 5: connect to your partners via EWP in the development environment

The full entry procedure is described in another part of the EWP Knowledge Base

 Step 6: rethink your internal business processes

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 a business process owner is directly involved in the rethinking of these processes.

 Step 7: identify a partner to test some data exchanges

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:

 Step 8: join the production environment

Once the basic APIs have been implemented and tested, you can be added to the production environment and officially accepted as an EWP partner.

 Step 8: start supporting mobilities using EWP

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

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

  • Nomination of mobilities 

  • Transcripts of Records

  • Access to Mobility Tool+ data dictionaries 

  • Learning Agreements

Some Instructional videos for the EWP Network (demonstration):

Related articles

Filter by label

There are no items with the selected labels at this time.