Whilst it would represent a lot of work it would be good to get non-blocking implementation (eg usin RxJava or Reactor) of the interfaces to allow for use in non-blocking codebases.
Thanks to the recent work on decoupling the implementation of API endpoints from the underlying HTTP client, this should be more feasible to achieve. It's on the roadmap, but no concrete timeline yet.
Currently the Nexmo Library is backed by a HttpClient using a PoolingHttpClientConnectionManager which is a blocking client.
Whilst it would represent a lot of work it would be good to get non-blocking implementation (eg usin RxJava or Reactor) of the interfaces to allow for use in non-blocking codebases.