Results
Exports and sharing
Export saved requests (APITestCenter, Postman, OpenAPI, .http, Markdown), save a report as HTML, Excel, JSON or a Zip, send it by email, or produce JUnit for CI dashboards.
Saved requests
Take requests out of the app — to share them, to move to or from another tool, or to document an API. Open Export from:
- a folder's ⋯ menu in the saved requests (or right-click it) → Export…;
- a request's ⋯ menu → Export…;
- Ctrl+K → Export requests — the whole project.
| Format | Good for |
|---|---|
APITestCenter (.apitestcenter) | Everything — folders, checks, Run first, saved values, scripts — to open in APITestCenter on another computer. Double-click the file and the desktop app opens with it, ready to import (or use Import requests) |
| Postman v2.1 | Teammates on Postman or Insomnia: folders, headers, bodies, Bearer/Basic/API-key auth, scripts |
| OpenAPI 3.1 | API docs, gateways and code generators: a path per address, {{variables}} in the path become path parameters, the base URL becomes a server |
| .http file | VS Code REST Client and JetBrains HTTP Client; the environment's values become @name = value lines |
| API docs (HTML) | One page to share or host — see API docs below |
| Markdown docs | A README or a wiki page: each request with its description, address, headers, body and checks |
The other files open, on a double-click, in whatever app your computer uses for them — .json in your editor, .http in VS Code, .md in a Markdown viewer. Postman and OpenAPI files go in through their app's own Import. Hover over a format to see what it's for.
What to export: Everything, or Pick folders and requests — a tree with checkboxes, where ticking a folder ticks everything in it, so you can take any mix of folders and single requests (with a search for long lists). Below it, choose whether the file carries example answers (the ones kept for the mock server — Postman gets them as examples), checks and scripts. Include an environment adds its variables. Save file downloads it; Copy puts it on the clipboard.
Secret values never go into the file. A token, password or API key typed into a request — in its auth, or in a header like Authorization or X-API-Key — is left empty; secret environment values are left empty too. {{variables}} are kept, so the file works again once the values are filled in.
API docs
API docs (HTML) makes one page from the requests you export: a list down the side with a search, then each request with what it's for, its address, query parameters and headers (with their descriptions), its body, its example answer, what it checks, and code that sends it — curl, JavaScript and Python. It starts with the exported folder's description, and each folder's own description heads its part. An included environment's variables are listed, secret ones without their value.
The page loads nothing from elsewhere, so it opens offline, works on any web server (GitHub Pages, an intranet, a shared drive), follows light and dark mode, reads on a phone, and prints well.
Write the descriptions on a request's Docs tab and in Folder settings → Docs, in Markdown: headings, bold, code, lists, tables, code blocks and links. Preview shows how it reads. Descriptions also go out with Postman, OpenAPI and Markdown exports, and come in with imports from Postman, OpenAPI, Insomnia and Bruno.
From a load-test report
The export bar above the report offers:
| Format | Good for |
|---|---|
| HTML | One page that opens in any browser, offline, and prints well. Follows your report view, starts with What happened in this run and suggested next steps, and has no scripts. |
| Excel | Three sheets — Overview, Result summary, and Second by second — for your own charts and records. |
| JSON | The full report. Open it again later with Open report, or feed it to your own tools. |
| Response JSON | The answer of the last Send. |
| Zip | All of the above in one file. |
Response JSON appears only when the report has a Send answer to go with it.
Share
Share opens a menu:
| Entry | What it does |
|---|---|
| Gmail | Opens a panel with the files to attach, then a Gmail draft with the summary. |
| Outlook on the web | The same, for Outlook on the web. |
| Default mail app | The same, through your computer's mail program. |
| System share | Hands the HTML and Excel files to your system's share sheet, where there is one. Otherwise it falls back to Default mail app. |
Browsers can't attach files to an email for you, so the panel offers them to download first: HTML report, Excel, and Zip, with JSON and Response JSON under Also available. It also has:
- Copy formatted summary — the Result, key numbers, response-time chart, goals, and checks (and the change against your reference run), ready to paste into any email or chat.
- Email draft with report attached (.eml) — a file that Outlook, Apple Mail, and Thunderbird open as a ready draft with the HTML report already attached. Add recipients and send.
Open Gmail (or Outlook on the web, or your mail app) then starts the email.
For someone without the app
Send the JSON or the Zip. They open it in the free report viewer in any browser: the whole report as you see it, with every chart, the written summary, and Excel and HTML exports of their own. Several runs of one API show the trend; ticking two or more compares them. Nothing is uploaded: their browser reads the file, and no account is needed.
From a compare
The export bar above the compare results offers:
| Format | Good for |
|---|---|
| Excel | Sheets Side by side (the key numbers and which API was best on each), Over time (each API's p95, requests per second, error rate, and users, second by second), Result summary (each API's result in plain words), and one sheet per API with its own summary. Needs at least two APIs. |
| JSON | The whole compare. Open it again later with Open report. |
| Response JSONs | A zip with each API's Send answer. Available when at least one API has one. |
| Zip | The Excel, the JSON, and the Send answers in one file. |
Share has the same four entries. The panel offers Download Excel and Download Zip to attach; the email lists each API and its key numbers, with the best one named. System share hands over the Zip. See Compare APIs.
From a collection run
HTML, JUnit (one test case per request — Jenkins, GitLab, Azure DevOps, and GitHub test reporters read it), and JSON. See Run a collection.
What never goes into an export
- Secrets. Auth appears as a type only (Bearer, Basic, API key), never the value.
- Filled-in values. URLs appear as you wrote them, with
{{variables}}, so tokens and ids from your environment don't leak. - Test data. Only the file name and the number of rows.