Automation and testing

Once a request works, make it work for you. Echo automates the repetitive parts: running suites, chaining calls, faking dependencies and checking on a schedule.

Run a whole collection

The collection runner executes a collection end to end:

  1. Choose the collection and set the number of iterations.
  2. Add a delay between requests if the target API needs breathing room.
  3. Turn on abort-on-error if one failure should stop the run.
  4. Start the run and watch results arrive live.

The runner is the quickest way to smoke test an API after a deploy or to reproduce a flaky behavior across many iterations.

Chain requests without code

Request chains are declarative: no scripting needed. A chain runs steps in order, and each step can extract values from a response with JSONPath and pass them to later steps. Sign in, grab the token, create a resource, verify it, all as one chain.

Steps can also carry conditions, so a chain can branch on what the API actually returned instead of blindly running everything.

Mock servers

When the real dependency is not ready, mock it locally. Echo's mock servers match routes with path patterns, answer with templated responses, and let you set delay and status per route. That means the frontend team keeps working while the backend endpoint is still a ticket, and you can rehearse timeouts and error codes on purpose.

Schedule runs

Cron-scheduled runs keep checking your API when you are not looking. Define the schedule, and Echo notifies you on failure, so a broken endpoint surfaces before your users find it. Schedules sync across your devices along with the rest of your signed-in work.

Script when you want to

For the cases that outgrow declarative chains, Echo supports pre-request and post-request JavaScript with the familiar pm.* API, including assertions. If you have written Postman scripts before, you already know how this works: assert on status codes, response bodies and headers, and fail the run when reality disagrees with expectations.

A good rule of thumb: reach for chains first, because they are easier to read and maintain, and use scripts where you genuinely need logic.

Next steps

  • Point your automation at the right environment: /docs/echo/environments-and-variables
  • Generate assertions, test suites and mocks with AI on a Pro AI seat: /docs/echo/ai-features