Specifications, Validators and Tools

Summary:

This document describes how EWP servers should declare that some of their endpoints can handle anonymous clients.

Summary:

This document describes how to accomplish EWP client authentication with the use of TLS Client Certificates.

Summary:

This document describes how to accomplish EWP client authentication with the use of HTTP Signatures.

Summary:

This document describes how EWP server authentication can be accomplished with the use of TLS Server Certificates, CAs, and the Registry.

Summary:

This document describes how EWP server authentication can be accomplished with signatures included in HTTP responses.

Summary:

This document describes how to accomplish confidentiality of EWP HTTP requests with the use of TLS transport.

Summary:

This document describes how to accomplish confidentiality of EWP HTTP requests with the use of ewp-rsa-aes128gcm encryption.

Summary:

This document describes how to accomplish confidentiality of EWP HTTP responses with the use of TLS transport.

Summary:

This document describes how to accomplish confidentiality of EWP HTTP responses with the use of ewp-rsa-aes128gcm encryption.

Summary:

This document describes the Institutions API. Once implemented by the host, it allows external clients to retrieve general information on institutions either covered, or otherwise known, by this host. This information includes things like address, logo image and key contact persons.

Summary:

This document describes the Organizational Units API. Once implemented by the host, it allows external clients to retrieve general information on selected organizational units (faculties, departments, divisions, etc.) either covered, or otherwise known by this host. It responds with similar type of information as Institutions API does, but on a lower level.

Summary:

This document describes the Courses API. This API is not directly related to EWP mobility APIs, but it might help with building user-friendly mobility client software. It allows other HEIs to access information on courses and other learning opportunities conducted in this institution.

Summary:

This document describes the Simple Course Replication API. This API can be implemented by any HEI, even it is does not take part in EWP mobility process. Once implemented, it allows the clients to replicate the catalogue of courses conducted on this HEI. This in turn allows the clients to design rich course searching user experience.

Summary:

This document describes the Interinstitutional Agreements API. This API allows partners to compare their copies of interinstitutional Erasmus+ mobility agreements with each other, which makes it easier to spot errors.

Summary:

This document describes the Interinstitutional Agreement CNR API. This API can be implemented by all EWP partners, and will be called by some other EWP partners whenever related IIAs are changed on their side. It allows the partners to listen for changes in other copies of their IIAs kept in the EWP Network.

Summary:

This document describes the Interinstitutional Agreements Approval API. This API allows HEIs to approve agreements sent by their partners in the Interinstitutional Agreements API.

Summary:

This document describes the Interinstitutional Agreement Approval CNR API. This API can be implemented by all EWP partners, and will be called by some other EWP partners whenever related IIAs are approved by them. It allows the partners to listen for approvals of their copies of the IIAs.

Summary:

This document describes the Mobility Factsheet API. This API allows partners to share all the information useful for incoming students in the mobility process.

Summary:

This document describes the Outgoing Mobilities API. This API is implemented by the sending institution. It allows the receiving HEI to read, write and enumerate mobilities stored on the sending HEI's servers.

Summary:

This document describes the Outgoing Mobility Learning Agreements API. This API is implemented by the sending institution. It allows the receiving HEI to read and accept Learning Agreements stored on the sending HEI's servers and propose changes to them.

Summary:

This document describes the Outgoing Mobility CNR API. This API is implemented by the receiving institution if it wants to be notified whenever mobilities kept on their partner institutions' servers are changed.

Summary:

This document describes the Outgoing Mobility Learning Agreement CNR API. This API is implemented by the receiving institution if it wants to be notified whenever learning agreements kept on their partner institutions' servers are changed.

Summary:

This document describes the Incoming Mobilities API. This API is implemented by the receiving institution. It allows the sending HEI to read the receiving HEI's "part" of the information related to the sending HEIs outgoing mobilities. (From the receiving HEI's perspective, these are the incoming mobilities.)

Summary:

This document describes the Incoming Mobility CNR API. This API is implemented by the sending institution if it wants to be notified whenever incoming mobilities kept on their partner institutions' servers are changed.

Summary:

This document describes the Incoming Mobility Transcripts of Records API. This API is implemented by the receiving institution. It allows the sending institution to retrieve Transcripts of Records issued by the receiving institution for a given set of mobility IDs.

Summary:

This document describes the Incoming Mobility ToRs CNR API. This API is implemented by the sending institution if it wants to be notified whenever Transcript of Records served by the receiving institution (via the Incoming Mobility ToRs API) are changed.