Skip to end of metadata
Go to start of metadata

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.

The implementation will need to be done by your IT team and therefore we encourage you to involve them in the process right from the beginning. From the one hand your IT team will 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 direct your IT team to and From the other hand 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 strongly involved in the rethinking of these processes.

Entry Process instructions: How can you join EWP?

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) to start the process.

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  ( We encourage technical people to participate actively there as all code is published there and issues discussed. 

The first concrete step is to send us the URL of your  manifest file.  It will then be entered in the 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.

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)

There is no content with the specified labels