I'm afraid the answer by @zoya.farberov is not quite fully accurate.
The strategy is indeed to provide REST API for request/response and Websocket API for streaming data retrieval via Eikon API Proxy. While the REST API is what underlies Eikon Python library, it is not yet documented for external consumption outside of Thomson Reuters. And the Websockets API is not ready yet altogether.

On top of these REST and Websockets APIs we intend to have a number of open source ease of use libraries similar to the existing Eikon Python library for a bunch of most popular development environments. Eikon Python library is the only one that will be officially supported by Thomson Reuters. The rest of them will be community owned. The first example of such library is the library for R, which is already available on GitHub.
https://github.com/ahmedmohamedali/eikonapir

Later on we plan to seed more of these libraries for other popular dev environments such as Matlab, .NET, Java. This is aspirational at the moment, there's no definitive list of libraries to be introduced or timeline to introduce them. If anyone wants to start a new library on GitHub for any of the dev environments I mentioned or any I did not mention, you'd be very welcome once the underlying REST and Websockets APIs are launched.

Currently, there is no plans to provide dedicated libraries other then Eikon Python.

Please refer to the Reference section to explore the available functionality and to the

Tutorials section for the best way to start working with Eikon Scripting Proxy