From OpenAPI spec to tested requests
Import an OpenAPI spec and get a collection of runnable requests in the Request Workbench. Then let continuous OpenAPI Sync surface drift the moment your spec and your collection disagree.
Upload a spec, get a working collection
Import an OpenAPI spec and every operation becomes a saved request in a collection — organized into folders, searchable by operation. No retyping paths, no copying schemas by hand.
Collections hold everything side by side: imported APIs next to requests you wrote yourself, with search across all of them. That makes OpenAPI testing a two-minute setup instead of an afternoon of data entry.
- "Import OpenAPI": spec upload → collection of requests
- Folders for structure, search for everything else
- Same import available from the CLI for scripting
Run any operation in the Request Workbench
Every saved request opens in a multi-tab editor with Params, Headers, Auth, and Body. Auth helpers cover the usual patterns, including API-key placement options, so you spend your time on the request — not on remembering where the key goes.
Requests execute server-side, and the response body and headers land right next to the request — a wrong status code or an unexpected content type is visible immediately. Edit, send, read, repeat — across as many open tabs as the investigation needs, with every request saved for the next session.
Catch API drift before your consumers do
Enable sync per collection and a background process reconciles spec changes on roughly a 30-second tick. Want an immediate answer? Trigger run-now and read the result. Because the configuration is per collection, a stable internal API can sit untouched while the fast-moving one reconciles continuously.
Every sync is recorded: the drift and sync history shows what was added, changed, or removed, and operation search takes you straight to the endpoint you're worried about. API drift stops being something you discover from a confused consumer.
- Per-collection sync configuration
- Run-now for on-demand reconciliation
- Drift and sync history, plus operation search
Scriptable imports from the command line
The same import runs from the terminal:
echopoint collections import --file openapi.yaml.
Wire it into the pipeline that builds your API, and collections track the spec
your team actually ships — not the one from last quarter.
The CLI is public on GitHub and installs with one checksum-verified command. See the CI/CD page for the full run-in-CI story.
echopoint collections import --file openapi.yamlImport, organize, execute, sync
Import
Upload a spec in the app, or run collections import --file from the CLI.
Organize
Folders keep collections tidy; search finds any operation across all of them.
Execute
Params, Headers, Auth, Body — server-side execution in the Request Workbench.
Sync
Enable per-collection sync, trigger run-now, and review the drift history.
Keep requests true to the spec.
Import your OpenAPI spec and run your first request in minutes — your workspace is provisioned on first sign-in. Free while in beta, no credit card.