HTTP to Postman Converter — HTTP Handoff

Turn your maintained .http and .rest request files into a Postman Collection v2.1 for customer handoffs and shared API examples. Regenerate the collection when your API requests change.

Supply named request files and any referenced text body files. Download one collection and its conversion diagnostics. The converter does not send your HTTP requests or execute source scripts.

Get started

1. Remove secrets from the files you intend to upload.
2. Enter the files as relative paths and text contents, as shown below, and run the Actor.
3. Open Storage > Key-value store in the run. Use the download action beside collection.json, and check diagnostics.json. Import the collection JSON in Postman and supply your environment values before sending requests. The Output tab also links to these files; if your browser blocks an inline preview, use the Storage download action.

{
  "files": [
    {
      "path": "api/items.http",
      "content": "@baseUrl = https://example.invalid\n### Items\nGET {{baseUrl}}/items?limit=10\n"
    }
  ],
  "collectionName": "Team API handoff",
  "includeLiteralCredentials": false
}

The example address is intentionally non-routable. Replace it with your API address before sending requests in Postman.

For repeated handoffs, invoke the Actor through the Apify API or CLI with updated file contents. Scheduling the same saved input will export the same content; this Actor does not watch or fetch your repository. The API tab provides the current integration endpoints.

What is preserved

• One Postman folder per source request file.
• File-scoped variables, nested variables, repeated query parameters and multiline URLs.
• Raw text and JSON bodies, including text files referenced inside the supplied folder.
• Basic and Bearer authentication syntax, subject to the credential setting below.
• A limited response-script adapter for client.test, client.assert, client.log, response.status and response.body.

Postman environment values override file defaults. This is an explicit export policy, not complete JetBrains runtime equivalence. Public environment JSON files are not automatically imported; supply their values in a Postman environment after download.

Limits and blocked input

Supply 1–200 text files, up to 5 MiB total, including at least one .http or .rest file. Relative paths use / separators and must fit within 240 characters. Absolute paths, traversal, duplicate paths, file/directory conflicts and request files in ignored build or metadata folders are rejected. The optional collection name is 1–120 characters.

Unsupported syntax blocks the entire collection with diagnostics. Examples include multipart bodies, dynamic/response-reference variables, external scripts, unsupported JetBrains runtime APIs, CONNECT and non-HTTP requests. Binary files are unsupported. The converter also caps a collection at 5,000 requests and 128 distinct file-variable names.

Data and credentials

Files are uploaded to and processed on Apify. Remove secrets before uploading. Run input, output and diagnostics remain in Apify storage according to your account's retention settings. Temporary conversion files are removed after normal completion; terminated containers follow platform cleanup.

Private environment files (http-client.private.env.json, .env and .env.*) are prohibited. With includeLiteralCredentials: false, recognized credential headers and sensitive file variables become empty placeholders. This is not comprehensive secret detection: secrets in bodies, query strings or unrecognized fields may remain. Credential omission happens after upload and does not sanitize the stored input.

Source scripts are included for later execution in Postman. Review them and the diagnostics before running or sharing a collection. The Actor does not forward your source files to another service.

Output and support

A result row shows conversion counts; it is not evidence of payment. Run output links lead to collection.json, diagnostics.json and the OUTPUT summary in the default key-value store. Blocked input produces diagnostics without a collection.

If output reports payment-uncertain, the saved collection remains available while the charge needs reconciliation. Do not submit a replacement run just to resolve that status. Contact the developer through the Actor's Issues tab with the run ID and a sanitized example; do not post credentials or confidential request files.

HTTP Handoff is independently developed and is not affiliated with or endorsed by JetBrains or Postman.