Tremendous work has been done to recognize the needs of the EWP Network stakeholders — staff of International Relation Offices, staff of Student Offices, and students themselves.

The answer to these needs is in the form of an Application Programming Interface (API) — a set of methods which can be used at the client side and server side of the university mobility system to transfer data in a digital form between a sending institution and a receiving institution. The API is described both in words and formally on the EWP GitHub website where every prospective development team can read it and comment. The architecture and security of the EWP Network is also specified in detail. The special developers guide is available at http://developers.erasmuswithoutpaper.eu/. This part of development is finished although new APIs and updates of the existing ones may be needed in the future as development progresses at participating institutions.

Development teams from participating institutions work on connectors which will connect local systems to the EWP Network. Every team can prioritize the set and order of APIs’ implementation according to local needs, available resources and technical expertise. As development is undertaken in an agile way, APIs become available for cross-testing as soon as possible. Integration testing between institutions either on artificial or real live data is in progress. Testing environment set by the University of Warsaw can be used by all partners.

Some extra tools for developers have been developed, e.g. Echo API Validator to validate the connection of the local system to the network and XML Document Validator for validating created XML files against the specification.

The User interface (UI) of the local mobility system depends on local needs. You may expect many Get data from EWP buttons for starting data transfer between partner institutions and many backend functionality carried by system daemons which implement Change Notification Request APIs. The final result from the end user point of view is that either the data from the partner is available upon entering the web page of the local system or with a simple click of the EWP button.