CallMe
A lightweight REST client for VS Code — test your APIs without leaving the editor, and jump straight from a response's stack trace to the exact line of code that handled it.
Why CallMe?
Most REST clients live outside your editor. CallMe lives inside it — and it does one thing existing tools don't: when your backend throws an error, CallMe parses the stack trace (or a custom X-Handler-Location header) in the response and lets you click straight to the file and line that handled the request, right in your open workspace.
Features
- One-click launch : a CallMe icon lives in the Activity Bar; click it to open CallMe as a full editor tab, no Command Palette required
- Full request builder : method, URL, query params, headers, and body (JSON, form-data, x-www-form-urlencoded, raw text, or none)
- Auth support : Bearer token, Basic auth, or API key, without hand-writing headers
- Source-jump navigation : click a stack frame in the error panel to open the exact file, line, and column in your workspace
- Handler location header : set
X-Handler-Location: routes/users.js:14 on your server responses for one-click jumps even on successful requests
- URL history : recently used URLs are remembered and suggested as you type
- Split response/error view : response body and error/stack trace shown side-by-side, each with a fullscreen toggle
- Built-in debug panel : a slide-out log (top-right of the panel) that tracks internal errors, failed jumps, and network issues as they happen, so you're not left guessing what went wrong
- Local-first : no accounts, no cloud sync, no telemetry; requests run entirely on your machine
Getting Started
- Install CallMe from the VS Code Marketplace
- Click the CallMe icon in the Activity Bar (left-hand strip), it opens CallMe as a full editor tab
- Alternatively, open the Command Palette (
Ctrl+Shift+P / Cmd+Shift+P) and run CallMe: Open
- Enter a URL (e.g.
localhost:3000/api/users), pick a method, and hit Send
That's it, no setup, no config file required.
Source-Jump Navigation
CallMe looks for stack traces in two places on error responses (status >= 400, or network failures):
- A
stack field in the JSON response body (res.data.stack or res.data.error.stack)
- The raw response body itself, if it's a plain-text stack trace
It also reads an optional X-Handler-Location response header, formatted as:
X-Handler-Location: routes/users.js:14
X-Handler-Location: routes/users.js:14:5
Click any parsed frame or handler location in the Error panel, and CallMe will:
- Resolve the file against your open workspace folders (absolute paths work too)
- Open it in the editor
- Place your cursor at the exact line and column
- Scroll it into view
If the file can't be found in your current workspace, CallMe will let you know rather than failing silently.
Request Options
| Feature |
Details |
| Methods |
GET, POST, PUT, PATCH, DELETE |
| Params |
Add key/value query params, appended to the URL automatically |
| Headers |
Add any custom headers; Content-Type is set automatically for JSON bodies |
| Body types |
JSON, form-data, x-www-form-urlencoded, raw text, or none |
| Auth |
No auth, Bearer token, Basic auth, or API key |
| URL shorthand |
localhost:3000/api works, CallMe assumes http:// if no protocol is given |
Requirements
Known Limitations
- Currently supports one request panel at a time per invocation of CallMe: Open
- No request collections/saving yet, URL history is the only persistence today
Feedback & Contributions
Found a bug or have a feature request? Open an issue on GitHub.
License
MIT — see LICENSE for details.
| |
