Monitor and troubleshoot Java applications and services with Datadog: 

>> Try it free!

1. Introduction

The HTTP protocol and APIs built on it are of central importance in programming these days.

On the JVM we have several available options, from lower-level to very high-level libraries, from established projects to new kids on the block. However, most of them are targeted primarily at Java programs.

In this article, we’re going to look at khttp, an idiomatic Kotlin library for consuming HTTP-based resources and APIs.

2. Dependencies

In order to use the library in our project, first we have to add it to our dependencies:


Since this is not yet on Maven Central, we also have to enable the JCenter repository:


Version 0.1.0 is the current one at the time of writing. We can, of course, check JCenter for a newer one.

3. Basic Usage

The basics of the HTTP protocol are simple, even though the fine details can be quite complicated. Therefore, khttp has a simple interface as well.

For every HTTP method, we can find a package-level function in the khttp package, such as get, post and so on.

The functions all take the same set of arguments and return a Response object; we’ll see the details of these in the following sections.

In the course of this article, we’ll use the fully qualified form, for example, khttp.put. In our projects we can, of course, import and possibly rename those methods:

import khttp.delete as httpDelete

Note: we’ve added type declarations for clarity throughout code examples because without an IDE they could be hard to follow.

4. A Simple Request

Every HTTP request has at least two required components: a method and a URL. In khttp, the method is determined by the function we invoke, as we’ve seen in the previous section.

The URL is the only required argument for the method; so, we can easily perform a simple request:


In the following sections, we’ll consider all requests to complete successfully.

4.1. Adding Parameters

We often have to provide query parameters in addition to the base URL, especially for GET requests.

khttp’s methods accept a params argument which is a Map of key-value pairs to include in the query String:

  url = "",
  params = mapOf("key1" to "value1", "keyn" to "valuen"))

Notice that we’ve used the mapOf function to construct a Map on the fly; the resulting request URL will be:

5. A Request Body

Another common operation we often need to perform is sending data, typically as the payload of a POST or PUT request.

For this, the library offers several options that we’re going to examine in the following sections.

5.1. Sending a JSON Payload

We can use the json argument to send a JSON object or array. It can be of several different types:

  • A JSONObject or JSONArray as provided by the org.json library
  • A Map, which is transformed into a JSON object
  • A Collection, Iterable or array, which is transformed to a JSON array

We can easily turn our earlier GET example into a POST one which will send a simple JSON object:
  url = "",
  json = mapOf("key1" to "value1", "keyn" to "valuen"))

Note that the transformation from collections to JSON objects is shallow. For example, a List of Map‘s won’t be converted to a JSON array of JSON objects, but rather to an array of strings.

For deep conversion, we’d need a more complex JSON mapping library such as Jackson. The conversion facility of the library is only meant for simple cases.

5.2. Sending Form Data (URL Encoded)

To send form data (URL encoded, as in HTML forms) we use the data argument with a Map:
  url = "",
  data = mapOf("key1" to "value1", "keyn" to "valuen"))

5.3. Uploading Files (Multipart Form)

We can send one or more files encoded as a multipart form data request.

In that case, we use the files argument:
  url = "",
  files = listOf(
    FileLike("file1", "content1"),
    FileLike("file2", File("kitty.jpg"))))

We can see that khttp uses a FileLike abstraction, which is an object with a name and a content. The content can be a string, a byte array, a File, or a Path.

5.4. Sending Raw Content

If none of the options above are suitable, we can use an InputStream to send raw data as the body of an HTTP request: = "", data = someInputStream)

In this case, we’ll most likely need to manually set some headers too, which we’ll cover in a later section.

6. Handling the Response

So far we’ve seen various ways of sending data to a server. But many HTTP operations are useful because of the data they return as well.

khttp is based on blocking I/O, therefore all functions corresponding to HTTP methods return a Response object containing the response received from the server.

This object has various properties that we can access, depending on the type of content.

6.1. JSON Responses

If we know the response to be a JSON object or array, we can use the jsonObject and jsonArray properties:

val response : Response = khttp.get("")
val obj : JSONObject = response.jsonObject

6.2. Text or Binary Responses

If we want to read the response as a String instead, we can use the text property:

val message : String = response.text

Or, if we want to read it as binary data (e.g. a file download) we use the content property:

val imageData : ByteArray = response.content

Finally, we can also access the underlying InputStream:

val inputStream : InputStream = response.raw

7. Advanced Usage

Let’s also take a look at a couple of more advanced usage patterns which are generally useful, and that we haven’t yet treated in the previous sections.

7.1. Handling Headers and Cookies

All khttp functions take a headers argument which is a Map of header names and values.

val response = khttp.get(
  url = "",
  headers = mapOf("header1" to "1", "header2" to "2"))

Similarly for cookies:

val response = khttp.get(
  url = "",
  cookies = mapOf("cookie1" to "1", "cookie2" to "2"))

We can also access headers and cookies sent by the server in the response:

val contentType : String = response.headers["Content-Type"]
val sessionID : String = response.cookies["JSESSIONID"]

7.2. Handling Errors

There are two types of errors that can arise in HTTP: error responses, such as 404 – Not Found, which are part of the protocol; and low-level errors, such as “connection refused”.

The first kind doesn’t result in khttp throwing exceptions; instead, we should check the Response statusCode property:

val response = khttp.get(url = "")
if(response.statusCode == 200) {
} else {

Lower-level errors, instead, result in exceptions being thrown from the underlying Java I/O subsystem, such as ConnectException.

7.3. Streaming Responses

Sometimes the server can respond with a big piece of content, and/or take a long time to respond. In those cases, we may want to process the response in chunks, rather than waiting for it to complete and take up memory.

If we want to instruct the library to give us a streaming response, then we have to pass true as the stream argument:

val response = khttp.get(url = "", stream = true)

Then, we can process it in chunks:

response.contentIterator(chunkSize = 1024).forEach { arr : ByteArray -> handleChunk(arr) }

7.4. Non-Standard Methods

In the unlikely case that we need to use an HTTP method (or verb) that khttp doesn’t provide natively – say, for some extension of the HTTP protocol, like WebDAV – we’re still covered.

In fact, all functions in the khttp package, which correspond to HTTP methods, are implemented using a generic request function that we can use too:

  method = "COPY",
  url = "",
  headers = mapOf("Destination" to "/copy-of-get"))

7.5. Other Features

We haven’t touched all the features of khttp. For example, we haven’t discussed timeouts, redirects and history, or asynchronous operations.

The official documentation is the ultimate source of information about the library and all of its features.

8. Conclusion

In this tutorial, we’ve seen how to make HTTP requests in Kotlin with the idiomatic library khttp.

The implementation of all these examples can be found in the GitHub project – this is a Maven project, so it should be easy to import and run as it is.

Monitor and troubleshoot Java applications and services with Datadog: 

>> Try it free!

newest oldest most voted
Notify of

Thanks for introducing us to kHttp.

Do you say this is a production ready plugin?


There isn’t a ton of movement on the codebase, so it should be pretty stable, just not under very active development.