[rhttp] Feature Request: Import Postman Collections and Environments

Extension

https://www.raycast.com/SebastianJarsve/rhttp

OS Version

No response

Description

Summary

Add support for importing Postman collection and environment export files in JSON format.

Problem

The extension currently supports only its own custom export format. Migrating APIs from Postman requires importing requests individually, such as through cURL.

This is impractical for companies managing hundreds or thousands of APIs. Postman is one of the most widely used API clients, so supporting its export format would make migration significantly easier.

Proposed Solution

Allow users to import:

• Postman Collection JSON files, including Collection Format v2.0 and v2.1
• Postman Environment JSON files
• Folders, requests, headers, parameters, bodies, authentication settings, and variables

Environment variables should be linked to imported requests where possible.

Acceptance Criteria

• Users can select and import a Postman collection JSON file.
• The collection's folder and request structure is preserved.
• Common request settings are imported correctly.
• Users can import Postman environment JSON files.
• Unsupported Postman features produce clear warnings.
• Importing large collections does not require converting every request to cURL.

Why This Matters

Postman is widely used by API development teams. Native import support would make this extension practical for organizations with large, existing API collections and remove a major barrier to adoption.

Who will benefit from this feature?

No response

Anything else?

No response

The issue names no files or tests; start by locating the rhttp extension and its current custom export/import path. Review how Postman collection and environment JSON represent folders, requests, settings, and variables. Done means supported formats import their structure and settings, environments link where possible, and unsupported features produce clear warnings.