GraphQL Summit is back for three days of insights, hands-on learning, and fun to celebrate the GraphQL community. Join us in San Diego Oct 3-5.
Docs
Try Apollo Studio

Subscriptions in Apollo Kotlin


By default, Apollo Kotlin uses the subscriptions-transport-ws protocol for subscriptions via the SubscriptionWsProtocol class. This protocol is no longer actively maintained. It remains the default for backward compatibility purposes.

A future version of Apollo Kotlin will change the default to the newer graphql-ws protocol and GraphQLWsProtocol class. If your server already uses graphql-ws, make sure to set your WsProtocol to GraphQLWsProtocol

Subscriptions are long-lived GraphQL read operations that can update their response over time, enabling clients to receive updates as they occur. They're usually implemented as a connection to a GraphQL server over WebSocket (including in Apollo Kotlin).

You define a subscription in your app just like you define a query, except you use the subscription keyword. Here's an example subscription for getting the latest value of a number whenever that number is incremented:

subscription NumberIncremented {
numberIncremented
}

Unlike with queries and mutations, a subscription operation can include only one field of the Subscription type. To subscribe to multiple fields, you create multiple subscription operations.

Setting the WebSocket URL

Because subscriptions usually use WebSocket instead of HTTP, you might have to customize the URL used:

val apolloClient = ApolloClient.Builder()
.webSocketServerUrl("https://apollo-fullstack-tutorial.herokuapp.com/graphql")
.build()

Note: Apollo Kotlin supports both https:// (or http://) and wss:// (or ws://) protocols. Internally, wss:// is renamed to https:// and which one you use does not matter.

Listening to a subscription

After you configure the NetworkTransport, use ApolloClient.subscribe to open the connection and listen for changes:

apolloClient.subscription(TripsBookedSubscription())
.toFlow()
.collect {
println("trips booked: ${it.data?.tripsBooked}")
}

Because subscriptions are long-lasting operations, they return a Flow<Response> instead of a single Response.

Terminating a subscription

Termination is handled through the coroutine scope. Cancel the coroutine to terminate the subscription.

By default, a single WebSocket is shared between all active subscriptions. When no subscription is active, the WebSocket is closed after a configurable timeout.

Error handling

Like queries, subscriptions support partial responses with GraphQL errors, which are emitted in the Flow.

Network errors terminate the Flow, and you need to retry to get new updates. Depending on the situation, retrying might open a new WebSocket or restart the subscription.

Customizing your WebSocket protocol

The GraphQL spec does not specify a particular protocol to use for subscription operations. By default, Apollo Kotlin uses subscriptions-transport-ws for backward compatibility purposes, but it supports all of the following:

To customize your protocol, use the WsProtocol interface. Apollo Kotlin comes with built-in support for the protocols above:

  • subscriptions-transport-ws: SubscriptionWsProtocol (default)
  • graphql-ws: GraphQLWsProtocol
  • appsync: AppSyncWsProtocol

For example, you can configure a graphql-ws transport like so:

val apolloClient = ApolloClient.Builder()
.webSocketServerUrl("http://localhost:9090/graphql")
.wsProtocol(GraphQLWsProtocol.Factory())
.build()
Edit on GitHub
Previous
Mutations
Next
GraphQL variables