A tool for building the Internet

Develop & test

We designed Dispatch for developers and testers. Use it for API consumption, testing, and development.

Manage

Have an extensive library of requests? Not a problem. Create them without repeating any configuration options. Stay DRY. Execute individual requests or launch a suite of requests at any time.

Why Dispatch?

Dispatch has a unique request templating mechanism. With templates, your request bodies become as simple as this:

{{ myBody }}

Dispatch fills that myBody object from its context. You are not repeating any JSON code in the request definitions. All reusable JSON goes to the templates, and the request definitions stay thin.

Dispatch also simplifies managing the authentication of requests. When you are using OAuth 2.0, or even with Basic Authentication, you have some settings to specify and manage. By moving these authentication related settins into Authentication Methods, authentication becomes easy to manage and you no longer need to repeat the same auth settings with every request.

The context object in the Dispatch app
Example use case

Dispatch has been used to manage a sizable collection of Kafka Connectors. The requests for creating Kafka Connectors have relatively large and almost identical JSON bodies. The common parts of the request bodies were handled using Dispatch's templating.

Features

  • Auth OAuth2, Basic auth, and Bearer tokens. You can define reusable authentication methods which allow for reusing auth definitions among different requests.
  • Templating Don't repeat yoursef
  • Environment variables with multiple environments like dev and production
  • Response inspection with response headers, status code and response body data.
  • Content types Dispatch excels with JSON, but the request bodies can be of any type
  • Export Export your requests as curl commands, or copy to clipboard for quick sharing.
  • Teamwork Dispatch saves the projects as readable JSON files. You can store them in your version control system.
  • Environments You can have as many environtments as you need. Variables defined in these environments can be used as query parmeters, request headers, request bodies, or in the request URIs.

Download

Download for Mac

Other download options