Monthly Downloads: 767,623
Programming language: Elixir
License: MIT License
Tags: HTTP    
Latest version: v0.14.0

finch alternatives and similar packages

Based on the "HTTP" category.
Alternatively, view finch alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of finch or a related project?

Add another 'HTTP' Package


[Finch](./assets/Finch_logo_onWhite.png#gh-light-mode-only) [Finch](./assets/Finch_logo_all-White.png#gh-dark-mode-only)

Build Status Hex pm Hexdocs.pm

<!-- MDOC !-->

An HTTP client with a focus on performance, built on top of Mint and NimblePool.

We try to achieve this goal by providing efficient connection pooling strategies and avoiding copying wherever possible.


In order to use Finch, you must start it and provide a :name. Often in your supervision tree:

children = [
  {Finch, name: MyFinch}

Or, in rare cases, dynamically:

Finch.start_link(name: MyFinch)

Once you have started your instance of Finch, you are ready to start making requests:

Finch.build(:get, "https://hex.pm") |> Finch.request(MyFinch)

When using HTTP/1, Finch will parse the passed in URL into a {scheme, host, port} tuple, and maintain one or more connection pools for each {scheme, host, port} you interact with.

You can also configure a pool size and count to be used for specific URLs that are known before starting Finch. The passed URLs will be parsed into {scheme, host, port}, and the corresponding pools will be started. See Finch.start_link/1 for configuration options.

children = [
   name: MyConfiguredFinch,
   pools: %{
     :default => [size: 10],
     "https://hex.pm" => [size: 32, count: 8]

Pools will be started for each configured {scheme, host, port} when Finch is started. For any unconfigured {scheme, host, port}, the pool will be started the first time it is requested. Note pools are not automatically terminated by default, if you need to terminate them after some idle time, use the pool_max_idle_time option (available only for HTTP1 pools).


Finch uses Telemetry to provide instrumentation. See the Finch.Telemetry module for details on specific events.

Logging TLS Secrets

Finch supports logging TLS secrets to a file. These can be later used in a tool such as Wireshark to decrypt HTTPS sessions. To use this feature you must specify the file to which the secrets should be written. If you are using TLSv1.3 you must also add keep_secrets: true to your pool :transport_opts. For example:

 name: MyFinch,
 pools: %{
   default: [conn_opts: [transport_opts: [keep_secrets: true]]]

There are two different ways to specify this file:

  1. The :ssl_key_log_file connection option in your pool configuration. For example:
 name: MyFinch,
 pools: %{
   default: [
     conn_opts: [
       ssl_key_log_file: "/writable/path/to/the/sslkey.log"
  1. Alternatively, you could also set the SSLKEYLOGFILE environment variable.

<!-- MDOC !-->


The package can be installed by adding finch to your list of dependencies in mix.exs:

def deps do
    {:finch, "~> 0.14"}

The docs can be found at https://hexdocs.pm/finch.