tapir, or Typed API descRiptions

Why tapir?

  • type-safety: compile-time guarantees, develop-time completions, read-time information

  • declarative: separate the shape of the endpoint (the “what”), from the server logic (the “how”)

  • OpenAPI / Swagger integration: generate documentation from endpoint descriptions

  • observability: leverage the metadata to report rich metrics and tracing information

  • abstraction: re-use common endpoint definitions, as well as individual inputs/outputs

  • library, not a framework: integrates with your stack


With tapir, you can describe HTTP API endpoints as immutable Scala values. Each endpoint can contain a number of input and output parameters. An endpoint specification can be interpreted as:

  • a server, given the “business logic”: a function, which computes output parameters based on input parameters. Currently supported:

  • a client, which is a function from input parameters to output parameters. Currently supported:

  • documentation. Currently supported:

Tapir is licensed under Apache2, the source code is available on GitHub.

Depending on how you prefer to explore the library, take a look at one of the examples or read on for a more detailed description of how tapir works!

Tapir is available:

  • all modules - Scala 2.12 and 2.13 on the JVM

  • selected modules (core; http4s, vertx, netty, aws servers; sttp and http4s clients; openapi; some js and datatype integrations) - Scala 3 on the JVM

  • selected modules (aws server; sttp client; some js and datatype integrations) - Scala 2.12, 2.13 and 3 using Scala.JS.


Is your company already using tapir? We’re continually expanding the “adopters” section in the documentation; the more the merrier! It would be great to feature your company’s logo, but in order to do that, we’ll need written permission to avoid any legal misunderstandings.

Please email us at tapir@softwaremill.com from your company’s email with a link to your logo (if we can use it, of course!) or with details who to kindly ask for permission to feature the logo in tapir’s documentation. We’ll handle the rest.

We’re seeing tapir’s download numbers going steadily up; as we’re nearing 1.0, the additional confidence boost for newcomers will help us to build tapir’s ecosystem and make it thrive. Thank you! :)

Adobe Colisweb Swissborg
Kaizo Process Street Tranzzo
Kelkoo group SoftwareMill Carvana
Moneyfarm Wegtam

Code teaser

import sttp.tapir._
import sttp.tapir.generic.auto._
import sttp.tapir.json.circe._
import io.circe.generic.auto._

type Limit = Int
type AuthToken = String
case class BooksFromYear(genre: String, year: Int)
case class Book(title: String)

// Define an endpoint

val booksListing: PublicEndpoint[(BooksFromYear, Limit, AuthToken), String, List[Book], Any] = 
    .in(("books" / path[String]("genre") / path[Int]("year")).mapTo[BooksFromYear])
    .in(query[Limit]("limit").description("Maximum number of books to retrieve"))

// Generate OpenAPI documentation

import sttp.apispec.openapi.circe.yaml._
import sttp.tapir.docs.openapi.OpenAPIDocsInterpreter

val docs = OpenAPIDocsInterpreter().toOpenAPI(booksListing, "My Bookshop", "1.0")

// Convert to akka-http Route

import sttp.tapir.server.akkahttp.AkkaHttpServerInterpreter
import akka.http.scaladsl.server.Route
import scala.concurrent.Future
import scala.concurrent.ExecutionContext.Implicits.global

def bookListingLogic(bfy: BooksFromYear,
                     limit: Limit,
                     at: AuthToken): Future[Either[String, List[Book]]] =
  Future.successful(Right(List(Book("The Sorrows of Young Werther"))))
val booksListingRoute: Route = AkkaHttpServerInterpreter()
  .toRoute(booksListing.serverLogic((bookListingLogic _).tupled))

// Convert to sttp Request

import sttp.tapir.client.sttp.SttpClientInterpreter
import sttp.client3._

val booksListingRequest: Request[DecodeResult[Either[String, List[Book]]], Any] = 
    .toRequest(booksListing, Some(uri"http://localhost:8080"))
    .apply((BooksFromYear("SF", 2016), 20, "xyz-abc-123"))

Other sttp projects

sttp is a family of Scala HTTP-related projects, and currently includes:

  • sttp client: the Scala HTTP client you always wanted!

  • sttp tapir: this project

  • sttp model: simple HTTP model classes (used by client & tapir)


Development and maintenance of sttp tapir is sponsored by SoftwareMill, a software development and consulting company. We help clients scale their business through software. Our areas of expertise include backends, distributed systems, blockchain, machine learning and data analytics.

Table of contents