request(); HttpUrl newUrl = originalRequest.url().newBuilder() .addQueryParameter("api_key", apiKey).build(); Request request = originalRequest.newBuilder().url(newUrl).build(); return chain.
proceed(request); }).build(); } [ full code on GitHub ] I like philippines mobile number example this kind of Java API for all but the simplest cases. Creating classes to represent remote APIs is a good abstraction method that works well with dependency injection, and having Retrofit create them for you from a customizable OkHttp client is remarkable. Other HTTP Clients for Java Since posting this article on Twitter , I've been excited to see people discussing which HTTP clients they use.
If none of the above are quite what you're looking for, take a look at these suggestions: REST Assured : An HTTP client designed to test your REST services. It provides a smooth interface for sending requests, as well as useful methods for making assertions about responses. cvurl : A wrapper class for Java 11's HttpClient, which solves some of the difficulties you might encounter when making complex requests.
Feign : Similar to Retrofit, Feign allows you to create classes from annotated interfaces. Extremely flexible, it offers many options for performing and reading queries, indicators, retries, etc.
Spring RestTemplate (synchronous) and WebClient (asynchronous) clients : If you've been using Spring for everything else in your project, it might be a good idea to stick with this ecosystem.
Baeldung has an article comparing them . MicroProfile Rest client : another client that works on creating a class from an annotated interface. Its interest is that it allows to reuse the same interface to also create a web server, being sure that the client and the server match. If you need to create both for this service, this is probably the one you need.
Summary There are plenty of choices when it comes to HTTP clients in Java. For simple use cases, I would recommend the java.net.http.HttpClient built-in client. For more complex use cases, or if you want to abstract your HTTP APIs as Java classes within a larger application, consider Retrofit or Feign instead. Happy coding, I can't wait to see what you build!If you're used to a statically typed language like Java, working with JSON can be difficult.