Dev Calls Guide

Dev Calls is a desktop API client for creating, testing and organizing HTTP calls and WebSocket connections. You can use it locally without an account, or sign in to sync your collections and collaborate with your team.

Start here

  1. 1Install and open Dev Calls.
  2. 2Select New collection to create a space for organizing your calls.
  3. 3Select New request and choose the HTTP or WebSocket protocol.
  4. 4Enter the URL and configure parameters, headers, authentication and body.
  5. 5Select Send to run the request.

To try an HTTP call right away, use the GET method with this URL:

https://httpbin.org/get

The response appears in the right-hand panel together with the status code and the execution time.

How the app is organized

The workspace is split into three areas:

  • Sidebar: collections, requests, environments, teams and settings.
  • Editor: method, URL and request configuration.
  • Response: HTTP status, content and headers returned by the server.

You can keep several requests open in separate tabs and switch between them quickly. Save your changes with ⌘S on macOS or Ctrl+S on Windows and Linux.

Creating an HTTP request

1. Choose the method

Dev Calls supports the most common HTTP methods, including GET, POST, PUT, PATCH, DELETE, HEAD and OPTIONS.

2. Enter the URL

Type a full URL, for example:

https://api.example.com/v1/customers

You can also paste a cURL command into the URL field. Dev Calls recognizes it and automatically fills in the method, URL, parameters, headers, authentication and compatible body.

3. Configure the request

Use the tabs below the URL:

  • Query: add query string parameters as key-value pairs.
  • Headers: add the HTTP headers required by the API.
  • Auth: configure authentication.
  • Body: enter the content to send.
  • Script: keep a pre-request script alongside the call.
  • Test: keep the test script associated with the call.

Every parameter or header row can be added, edited, disabled or deleted without losing the structure of the request.

4. Configure authentication

The available options are:

  • No authentication
  • Basic Auth, with username and password
  • Bearer Token
  • API Key, sent in a header or in the query string

Never share collections that contain real credentials. Use environment variables for tokens, hosts and sensitive values.

5. Add a body

You can prepare JSON, XML, text, HTML, binary, multipart, form URL encoded, GraphQL and file upload bodies. Also set the Content-Type expected by the API when it is not added automatically.

Reading the response

After sending, the Response panel shows the status code and the elapsed time. The content can be inspected in several modes:

  • Formatted: makes structured formats easier to read.
  • Raw: shows the original content.
  • Preview: renders compatible content.
  • Tree: lets you explore structured data.
  • Headers: shows the received headers.

You can search text in the response, jump between matches, format or minify the body and copy the content to the clipboard. From the request menu you can also copy the equivalent cURL command.

Using environments

Environments let you reuse the same collection with different configurations, for example development, staging and production.