Presentation given at OR2019 Hamburg DSpace 7 is a major update of the DSpace platform with a new substantial different architecture than previous DSpace versions. The need to provide a fully-fledged REST API layer on top of which the new Angular (javascript) UI has been built was the opportunity to move to updated technologies, standards and best practice for the REST layer previously quickly introduced in the DSpace landscape to meet urgent needs of interoperability. Indeed, the goal of the new REST API is to meet the level 3 of the famous Richardson Maturity Model [1] allowing a client application or its developer to potentially learn how to use the API without pre-knowledge or need to consult external information. The adoption of uniform, consistent and self-documented behaviour will drastically reduce the effort for developers to interact with DSpace. Moreover, each operation that can be performed from the UI as an anonymous user or a user with whatever privilege, including repository managers and administrators, can now be done via a standard REST API. To offer a strong interoperability layer is crucial to provide a stable, well documented and fully tested solution so that integration will not easily break from one version to another: for this reason the REST development adopted a Test-Driven Development and Contract [2] first approach. The presentation will illustrate the adopted standards HATEOAS [3], HAL [4], JWT [5], ALPS [6] showing how to interact with the new REST API to get and manipulate information. Different integration scenarios will be presented explaining how the new REST API can be used to implement them. This will include reuse of the information available in DSpace in other contexts such as personal, departmental or institutional websites. Integration of DSpace in research workflows for data acquisition, embedding of the repository in wide institutional processes like ETD preparation triggering workflow automation in response of external events. Quickly prototyping end users functionalities such as notification services, reporting tools, batch processing in the language of preference of developers. The development processes and technologies [7] will also be quickly introduced as a reference to provide direction to those interested in customizing the new REST API or to participate in its future development.