SrcNexus Logo
Back to Marketplace
REST Client

REST Client

v1.0.2

by Extensions Maker

Send HTTP requests from the editor and read the response — no CORS, real headers, cURL import/export, binary-safe responses and saved history

ToolsUtilities

REST Client

Hit an API and read the response without leaving the editor — and without a browser's CORS rules getting in the way.

Why it works where a browser tab doesn't

Requests are sent through the app's own network layer, not the WebView's. That means:

  • No CORS preflight — you can call an API that has no Access-Control-Allow-Origin header.
  • Real headers — Authorization, Cookie and friends go out exactly as you typed them.
  • Response headers come back in full, not filtered down to the CORS-safelisted ones.

    • Features

  • All the usual methods — GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS.
  • Query parameters in their own editor, encoded for you. A query typed into the URL is pulled into the editor when you send.
  • Auth tab — Bearer token, Basic (username + password, encoded for you), or a custom header. An explicitly typed header always wins.
  • Body with a content-type picker (JSON, form URL-encoded, plain text, XML) that sets Content-Type automatically, plus Format and Minify for JSON.
  • cURL both ways — build a cURL command from the current request, or paste one in and load it into the form.
  • Status, round-trip time and response size at a glance; 3xx reads as a redirect, not a failure.
  • JSON is pretty-printed automatically, with the untouched body on a Raw tab.
  • Binary responses are handled as binary — an image, PDF or archive is described and previewed as hex rather than mangled into text, and saves to disk byte-for-byte.
  • Save the response to a file, with a name suggested from the content type.
  • History — the last 20 requests, tap one to load the whole form back. Saved requests are pinned and survive Clear.

    • Usage

  • Tools menu → REST Client — full tab
  • Drawer → REST — bottom sheet over your code
  • Command palette → Open REST Client

    • Permissions

    fileSystem — only used by Save to file, which can write outside the current project. You are prompted the first time, and can grant it once, for the session, or permanently. Requests themselves need no permission.

    How binary responses work

    The body always comes back from the host base64-encoded, because the content type is only known once the response arrives and decoding image bytes as UTF-8 destroys them. Textual responses (text/*, JSON, XML, HTML, CSV, YAML, and anything with no content type) are decoded and displayed; everything else is reported as binary with its size, type and a hex preview, and the original bytes are written straight to disk when you save.

    Textual responses above 4 MB are not rendered either — they can still be saved to a file.

    Notes

    History keeps the URL, method, headers, auth and body you typed — including any tokens. Clear it from the History tab if you are handing the device to someone else.