Skip to content

Debugging tools

Expand the console at the bottom of the window (⌘⇧C / Ctrl+Shift+C on desktop, Alt+Shift+C on web). It has these tabs:

  • Network — every request Restura sends, with method, status, timing and the request and response details. Credentials are redacted in what the console shows and exports: credential and cookie headers, secret-looking query parameters and JSON fields, and recognisable tokens in bodies appear as [REDACTED].
  • Frames — messages from streaming connections, filterable by protocol and searchable, optionally grouped by connection.
  • Timeline — the same traffic across WebSocket, Socket.IO, SSE, Kafka and MQTT in one arrival-ordered view. See Streaming timeline.
  • Disk desktop only — the persistent request log kept on disk (HTTP and gRPC, newest first), so you can look back at requests from earlier sessions. It records method, URL, status, duration and any error — not headers or bodies — so reopening an HTTP entry gives a safe draft with just the method and URL (gRPC entries can’t be reopened).
  • Scripts — script output and test results for the runs in this session.

From the console toolbar you can pause capture (new entries and frames are dropped while paused), toggle Preserve log (when off, earlier entries are cleared on each send), clear the log, and export all or only the filtered entries as HAR, NDJSON or cURL.

There are two ways to diff responses:

  • Compare with previous — once a request has an earlier response in history, the response toolbar’s Compare with previous response button diffs the two. The button is hidden when there is nothing to compare. See HTTP / REST.
  • Compare two console entries — in the Network tab, tick the compare checkbox on two entries (or use Select for compare in an entry’s context menu), then choose Compare (2) in the entry detail pane.

Both open the same dialog: request and response headers side by side with differences highlighted, and request and response bodies as a unified line diff.

A script can add your own HTML view of the response. In a test (or pre-request) script, call rs.visualizer.set(template, data) (pm.visualizer.set also works); the response panel then offers a Visualize tab. The tab goes away on the next send that doesn’t call visualizer.set.

The template runs in a sandboxed iframe with scripts allowed, but with no same-origin access and a Content-Security-Policy that blocks every network request, so a template can’t read Restura’s state or call out. Only inline styles and scripts and data: images work, and the rendered document is capped at 1 MB. The template is plain HTML — it is not run through Handlebars as in Postman, so {{…}} placeholders stay literal. Read the data from an inline script instead: pm.getData() returns the value you passed. See Scripts.

desktop only The desktop app registers the restura:// scheme. A deep link only opens an existing, reviewed UI action — it never sends a request or imports data without your confirmation.

LinkWhat it does
restura://import?url=<encoded URL>&format=postmanOpens the import dialog with the source URL, ready to review and download
restura://environment?id=<environment-id>Makes that environment active and opens the environments panel
restura://collection?id=<collection-id>Selects that collection in the sidebar
restura://request?id=<saved-request-id>Opens that saved request in a tab
restura://settings?section=securityOpens Settings at that section

For import, format is optional and may be postman, insomnia, openapi, opencollection, hoppscotch, bruno or http. The source must be a public URL without embedded credentials, and the download is HTTPS-only. Nothing is downloaded until you choose Download preview in the import dialog; every redirect and target passes the normal URL and DNS checks, and the result goes through the usual import review before anything is saved. See Desktop deep-link imports.

section may be general, appearance, requests, proxy, certificates, security, secrets, ai, data, updates, shortcuts or about. IDs may contain only letters, digits, - and _ (up to 128 characters).

A link that doesn’t match one of these shapes exactly — an unknown route, extra or repeated query parameters, a #fragment, or an ID that doesn’t exist — is ignored. Links that arrive while the app is starting are queued and applied once your collections and environments have loaded.