fetchdsl.dev

What it is

FetchDSL is a compact DSL for scripting HTTP requests. The text says it runs on top of Kotlin, Ktor, and kotlinx-coroutines, with the goal of making it faster to write and maintain bulk HTTP requests. Its core entry point is runHttp; each context is similar to an “incognito browser window”: cookies and state can be shared within the block, but once the block ends, a new context starts from a clean state. Multiple runHttp instances can also run in parallel on different threads, with no global state.

Core capabilities

In terms of functionality, it is more than a simple wrapper around GET/POST; the focus is on high-volume request workflows. call can be used to configure the request method, body, and other options. DataSupplier provides different parameters for each request. In the examples, FileDataSupplier reads a file line by line and replaces placeholders such as !1! and !2! in the request body or other fields, making it suitable for scenarios like bulk adding items to a cart or downloading a list of URLs. The hook mechanism is another highlight: Before Hooks can run logic before a request is sent, SkipIf can skip unnecessary requests, Once ensures a hook runs only once, and SessionPersistingBeforeHook can perform preliminary requests under the same Cookie Jar, which is useful for cases such as CSRF tokens. For After Hooks, LogResponse is mentioned as a way to output responses.

Language support, ecosystem, and documentation

It is clearly aimed at Kotlin/JVM developers and depends on the Ktor and coroutine ecosystem. The upside is that the syntax is friendly to Kotlin users and can take advantage of coroutines for high-concurrency, low-resource request tasks. The downside is that non-Kotlin users may face a relatively high migration cost. The documentation includes quite a few examples and helps explain the execution model, parameter replacement, and hook concepts. However, the text also contains TODOs, truncated content, and a few suspected spelling or variable issues. Key information such as installation methods, versions, license, and output storage is not fully presented, so the documentation feels only moderately mature.

Pricing, pros, and cons

The captured text does not provide pricing, payment methods, commercial services, or open-source license information, so its business model cannot be assessed. Its strengths are a concise DSL, clear state isolation, practical bulk parameterization, and extensible hooks. Its weaknesses are incomplete public information, unclear ecosystem integration, maintenance status, and support channels. It is not suitable as a direct replacement for Postman/JMeter for users who need a mature GUI, team collaboration, or enterprise-grade support.

Who it is for and access from China

It is suitable for developers familiar with Kotlin who want to manage HTTP batch processing, API automation, simple scraping, or session-based request workflows in code. The text does not provide information about access from China, so it is unclear whether the domain is directly reachable. There is also no payment information. If access or ecosystem support is inconvenient, alternatives include curl, HTTPie, Postman, Insomnia, Ktor Client, k6, or JMeter.