URL Import, Filter History, and GraphQL Schema Files

The Import Data dialog now takes a URL or a dropped file, and a new OpenAPI importer handles large schemas, creates an environment per server, and imports auth the way Yaak inherits it. Community contributions bring response filter history with pinning and GraphQL schemas loaded from a file.

🔗 Import from a URL

The Import Data dialog now accepts a URL alongside file selection, so a Swagger or OpenAPI spec served by your API can be imported without downloading it first. The dialog itself also picked up drag-and-drop for files.

🕘 Filter history with pinning

The response filter box now remembers your recent JSONPath and XPath expressions. Open the dropdown to pick one, pin the ones you reach for constantly so they stay at the top, or clear the list.

📄 GraphQL schemas from a file

GraphQL autocomplete and the documentation explorer no longer depend on live introspection. Load a schema from an SDL or introspection JSON file from the Schema menu, useful when introspection is disabled on the server or you are working offline. Automatic reload keeps it fresh as the file changes.

📥 New OpenAPI importer

OpenAPI 3.x and Swagger 2 documents are now parsed directly into Yaak instead of round-tripping through the Postman converter. Large schemas that used to fail on import now work, and the result matches what the spec describes:

• Each servers entry becomes its own sub-environment with baseUrl and credentials, so switching between production and sandbox is an environment change.
• Spec-level security imports as workspace authentication that requests inherit, with client IDs, secrets, API keys, and tokens as environment variables.
• Request bodies generate from schemas, including XML, and parameters follow the spec’s serialization rules.
• OpenAPI 3.2 QUERY and additional operations import.

🔌 Plugin API for reading response bodies

Plugins can now read response bodies directly, with fetch-style helpers for text, JSON, and streaming, instead of opening files off disk. Charset decoding and large bodies are handled automatically.

Breaking change for plugin authors. ctx.httpRequest.send() now resolves to { httpResponse, body }; plugins that read response bodies will need updating.

const { httpResponse, body } = await ctx.httpRequest.send({ httpRequest });
const data = await body.json();