Hey, API World! Take a look at what we shipped in v2022.16.0
of HTTPie for Web & Desktop 👇
🔖 Abstract
📯 Import your Postman and Insomnia knowledge to HTTPie
Since our public beta launch just a few months in the past, the adoption of HTTPie for Net & Desktop has been rising. A lot of our new customers have migrated from different API testing shoppers like Postman and Insomnia, they usually’ve been asking for a smoother migration path.
So on this launch, we centered on streamlining the migration course of, and—along with the prevailing cURL import—now you can import complete collections, environments and knowledge dump zips from Postman and Insomnia.
🚀 Migrate to HTTPie in just a few easy steps
- Export your knowledge from Postman or from Insomnia.
- Open the import dialog (Library → “+” → “Import…”).
- Drag & drop the exported file and click on “Subsequent…”.
- Choose the goal house and click on “Import.”
- Achieved! Welcome to HTTPie 🤗
💡 Tip: Create a brand new house throughout the import to maintain issues tidy.
🛂 Import compatibility
Right here’s an outline of what parts HTTPie at present imports from Postman and Insomnia and the way. As we regularly add new options to HTTPie, we’ll proceed to enhance the import as properly.
🛫️ Importing requests
| Request component | Imported? | Notes |
|---|---|---|
| HTTP Requests | ✔ | |
| GraphQL requests | ✔ | |
| gRPC requests | ✘ | |
| WebSockets | ✘ | |
| Request methodology | ✔ | Together with customized ones. |
| Request URL | ✔ | |
| URL parameters | ✔ | |
| Headers | ✔ | |
| Auth | ✔ | Primary, bearer, API key, and inherited auth. |
| Physique | ✔ | Textual content, uncooked, JSON, and kind request our bodies. |
| Physique information | ✘ |
🍱️ Importing containers
| Container | Imported? | Notes |
|---|---|---|
| Collections | ✔ | See assortment variables under. |
| Sub-folders | ✘ | Folder hierarchy is preserved as breadcrumbs in request names. |
🖼️️ Importing environments & variables
| Ingredient | Imported? | Notes |
|---|---|---|
| Environments | ✔ | |
| Default variables | ✔ | |
| Assortment variables | ✔ | We transfer non-global variables to the house stage and refactor names and references to make sure uniqueness. |
💧 Importing different parts
| Different component | Imported? | Notes |
|---|---|---|
| Scripting | ✘ | Pre-request scripts, checks, and dynamic tags. |
| Meta knowledge | ✘ | Schemas, documentation, area descriptions, and response examples. |
| Customized settings | ✘ | |
| Cookies | ✘ |
🪄 Simpler GraphQL APIs testing with schema assist
When speaking to GraphQL APIs, HTTPie will robotically fetch the schema from the server. Which means the app is now conscious of all of the obtainable queries, mutations, and the hierarchy of varieties, which permits us to spice up your productiveness with auto-complete and validation.
See auto-complete solutions as you kind, and to invoke the menu manually, press ⌃House.
HTTPie auto-fetches the schema utilizing the present request’s URL and authentication. To refresh the schema, choose “Replace from server” from the brand new “Schema” menu. And to disable schema for a specific tab, uncheck “Auto-apply schema.”
Along with schema assist, the GraphQL shopper now comes with code folding and different quality-of-life enhancements.
✨ Different enhancements
- Improved cURL import with assist for ANSI-C quoting shell syntax (e.g.,
$'string'). This syntax is utilized by Chrome DevTools when exporting a request that features a physique as cURL, amongst others. - HTTPie for Desktop now remembers the window’s place. This manner, you do not have to maneuver it each time you launch it.
- On HTTPie for Home windows, the title bar colour now respects the system.
- The request definition tables now not soar when switching tabs.
- We’ve added error boundaries to tabs and different elements for extra sturdy exception dealing with and restoration.
- The textual content search had some points with very lengthy strains. Now it’s fastened.
- Spelling and autocorrect within the filter area is now disabled.
🤩 Joyful API testing, and see you once more quickly!
Initially revealed on HTTPie blog.
