Echo on Android and iOS

Echo Mobile lets you send requests, check responses and work with your collections away from your computer. Use the links on the downloads page to open the appropriate store. The mobile app has its own interface, so some desktop tools have no equivalent screen on your phone.

Start with a request

  1. Open Collections. Create a space if you do not have one, then add a collection inside it.
  2. Open the collection and add a request. New requests on mobile start as HTTP requests.
  3. Give it a name, choose the method and enter the URL your device can reach.
  4. Use Params, Headers, Body and Auth to complete the request. Parameter and header rows can be enabled or disabled without removing them.
  5. Tap Send. While the request is running, the same area offers Cancel.
  6. Open Response to inspect the result. Changes to an editable request are saved automatically; you do not need a separate save step before sending.

You can work with the data on your device without signing in. Sending a request still requires access to its target API. If the API runs on your computer, localhost on the phone refers to the phone itself. Use an address reachable from the phone and check the network or VPN connection.

The on-device database is encrypted, and its key is kept in the operating system's secure storage. Keep your screen lock enabled, particularly when collections contain credentials or private responses.

Bring your desktop collections

Sign in from Settings with the same Gapfy account you use on the desktop. If you belong to several organizations, select the matching workspace before looking for its collections. Pull down the collections or environments list to synchronize, or use Sync now in Settings.

Collections, requests and environments can follow you between devices. Request history and cookies stay on the device where they were created. A synchronization error means the latest changes may not have reached the other device yet. Check the status and sign in again when the app asks you to.

Collections shared by another person appear under Shared with me, grouped by the person who shared them. Read access allows you to open and send requests without changing the saved collection. Editing requires the appropriate contribution access. Configure sharing through the desktop or Maestro workflow.

Choose an environment

Open Environments to create an environment and edit its variables. Save each variable after changing its name or value. Mark passwords and tokens as Secret to hide their values in the editor; use Show only when you need to inspect one.

Select Set active in the list, or tap the environment name beside Send and choose one there. No environment clears the selection. A request such as {{baseUrl}}/orders uses the selected environment when sent. If a placeholder remains unresolved, first check the selected environment and the variable name.

Key Vault references synchronized from the desktop retain their reference type on mobile. They do not become ordinary text secrets when saved. The mobile app cannot retrieve the referenced Key Vault secret, so a request that needs one cannot run there. Use a suitable mobile environment or run that request on the desktop. See environments and variables.

Authentication and response details

Bearer, Basic and API key authentication have dedicated fields. API keys can go in a header or query parameter. Other authentication types expose their configuration as JSON; they do not have the desktop's full setup screens. A saved authentication type alone does not guarantee that its interactive flow is available on mobile.

The response includes the status, duration, time to first byte, size and headers. You can switch between highlighted and raw body views and copy the displayed body. Large bodies are truncated in the viewer, and a saved history entry keeps only an excerpt. A truncated view is not the complete response.

Results from existing request tests and script console messages appear with the response. The mobile interface does not include a script editor. Prepare scripts on the desktop and synchronize the request before running it on your phone.

History supports URL search and filters for successful responses, HTTP errors and transport failures. Tap an entry to reopen its request. Up to 200 executions are kept per request on the device. Home also provides shortcuts to recent requests.

Protocols and larger screens

The shared execution engine handles HTTP, GraphQL, WebSocket and SSE. gRPC has partial support, including unary calls and reflection in the engine; client certificates and stream visualization are limited. Settings shows the capability summary for the device.

Create and configure advanced protocol requests on the desktop before synchronizing them. The mobile editor does not provide a protocol selector, a gRPC service browser or the desktop's interactive streaming panels. It also has no screens for collection runners, chains, schedules, mock authoring, import and export, or AI assists. Use the relevant desktop guides for those tasks.

In landscape on a sufficiently wide screen, the collection list and its request can share the screen. The request editor can also show its response beside the request when there is enough room. Settings offers system, light and dark themes and accent colors. The interface follows the device language.

Resolve a connection or synchronization problem

If Android asks for Nearby devices permission before a request to your network, allow it to reach that endpoint. When permission has been denied, the app offers a link to its system settings. Public endpoints and network endpoints can have different access requirements.

Reset local data in Settings is a recovery action for data stored on this device. It asks for confirmation and is unavailable during synchronization or a workspace change. Already synchronized spaces, collections, requests and environments can download again after sign-in. Unsynchronized changes, request history and cookies on this device are permanently lost. Read the confirmation carefully before using it.

Use Feedback in Settings to report a problem with a short description of what you were doing. Include the protocol and the error shown, and remove credentials and private response data.