Limits and FAQ
What Vizroute does not do, the size limits, fixes for the problems people hit most, and answers to common questions.
Most problems come from one of two places: the browser blocking a request to another site, or a size limit. Both are covered here, along with what Vizroute does not do.
What it does not do
- GraphQL and gRPC schemas are not read.
- Postman scripts are not run. Pre-request and test scripts are shown in the inspector, not executed.
- The mock server does not serve anything. It makes up example responses, and gives you no address to call.
- Test flows are not saved. Copy the steps as cURL if you want to keep them.
- Saved work is not synced between browsers or devices, even with a connected account.
- The JSONPath tester runs JSONPath only, not jq or JMESPath.
- A shared link is not a shared workspace. Changes made after you send it stay on each side.
Limits
| What | Limit |
|---|---|
| Recent APIs | The last 8 |
| Saved collections | 20. The oldest is dropped when the list is full |
| Services in one Contract Graph workspace | 60 |
| Contract Graph share link | 16,000 characters |
| API Map share link and embed | 200,000 characters of specification, and 16,000 characters of link after compression |
| Text editor on the import screen | About 600,000 characters. Larger files still load, without the editor |
| Health monitor | The first 25 endpoints by default. It asks before checking more than 50 |
| Load tester | Up to 200 requests from up to 50 simulated users |
| NDJSON viewer | 5,000 records |
| SOAP Workbench, where it is on | 300 services per programme, and a WSDL up to 25 MB |
Troubleshooting
"CORS blocked" when loading a URL. The server does not let a browser on another site fetch the file. Download the file and use Upload. For a file on GitHub, use the raw file address.
A request fails in the playground but works in Postman or curl. Postman and curl are not browsers, so cross-origin rules don't apply to them. Read the playground's message. It tells you whether the server refused a request from a browser, or whether nothing answered at all. Use Copy as cURL and run the request from a terminal.
"This path has no host". The specification gives only a path, such as /v1/orders. Enter the base URL the playground asks for, or put it in an environment.
"too large to travel in a link". The specification doesn't fit in a share link. Use Download spec and send the file.
"Browser storage refused this specification". The file is too big for your browser's storage. Delete old collections and try again, or keep the file on disk.
A recent API says its stored copy is gone. Your browser cleared it to free space, and the entry has been removed. Load the file again.
A WSDL will not open. The status line gives the reason. A WSDL that imports its schemas from separate XSD files needs those files too, and the API Map reads one file at a time. The SOAP Workbench, where it is switched on, attaches XSDs dropped together with their WSDL.
The Contract Graph tabs are missing. They appear only when a workspace has services, and only in a wide window. Widen the window or zoom the browser out.
A tool I read about is missing. Open the command palette with Ctrl+K and type its name. Several API Map tools have no button of their own.
Questions
Is my specification uploaded anywhere? No. It is read and drawn in your browser. Accounts and privacy lists the few actions that send something out, all started by you.
Do I need an account? Only for Contract Graph and the Postman companion.
Is it free? Yes. There is no paid tier, and nothing asks for a card.
What happens if I clear my browser data? Everything you saved goes: recent APIs, collections, environments, keys and Contract Graph workspaces. A local account goes too. Download any workspace you want to keep first.
Can my team share a workspace? Not as a live, shared workspace. Send a share link, or download the workspace file and have them import it.
Can I use it offline? Once the page has loaded, reading a file you already have, the map, the audit and the Explore Tools all run in the browser. Anything that fetches a URL or sends a request needs a connection. Offline use has not been tested beyond that.