Skip to content
Echopoint Echopoint Docs

Echopoint documentation

Echopoint is an API flow automation and testing platform. You build visual API flows with a real assertions engine, then run those flows from the cloud, your own infrastructure, or CI. Webhook capture is included when you need to inspect incoming requests.

The four pillars

Section titled “The four pillars”
  • Flows with assertions. Chain HTTP requests on a visual canvas using nine node kinds, from Request and Delay to Branch, Loop, Poll, and SSE. Extract values from responses and assert on them with 14 operators — every assertion is recorded with expected vs actual, even when it passes. See Building flows and Outputs & assertions.
  • Run anywhere. Launch flows from the UI, the CLI, the API, a GitHub Action, or a recurring schedule. Executions run on the managed cloud runner, on a self-hosted runner in your infrastructure, or as an ephemeral runner inside a CI job — with live node-by-node progress either way. See Runners and CLI.
  • OpenAPI import and sync. Turn a spec into a collection of runnable requests in one import, then keep the collection reconciled as the spec changes — with a drift history of added, changed, and removed operations. See OpenAPI import & sync.
  • Live webhook capture. Create an inbound endpoint with just a name and get a capture URL immediately. Requests stream into the app in real time over SSE, and you inspect headers, query parameters, and bodies per request. See Webhook testing.

Mental model

Section titled “Mental model”

Six building blocks make up the product. Each maps to a section of the app sidebar and a section of these docs:

  • Webhook endpoints — inbound capture URLs of the form https://api.echopoint.dev/webhook/{id}. No auth required to send; every request is stored and streamed live. → Webhook testing
  • Collections and requests — saved, executable HTTP requests organized in collections with folders. Built manually in the workbench or generated from an OpenAPI spec. → Request workbench
  • Flows — visual graphs of nine node kinds — Request, Delay, Module, Set Variable, Assert, Branch, Loop, Poll, and SSE — connected by success and error edges, with outputs and assertions per node. → Building flows
  • Executions and runners — individual flow runs with per-node results, assertion records, and live SSE progress. Executions are claimed by cloud, self-hosted, or ephemeral runners, and can start on a recurring schedule. → Executions & live runs, Scheduled runs, Runners
  • Environments — organization-level default variables with named overlays such as staging or prod, plus flow-level variables. Pick an environment at launch. → Environments & variables
  • API keys — org-scoped keys with scoped permissions (for example flows:execute) and a curated ci preset, used by the CLI, the API, and the GitHub Action. → API keys & permissions

Where to start

Section titled “Where to start”

If you are new, follow Getting started. It walks the full path: sign in, capture a webhook live, import an OpenAPI spec, build a flow with an assertion, and run it from CI.

If you already know what you need:

Next steps

Section titled “Next steps”