One-time downloads · $0.99 USD. No subscription.

Perunlight

RequestParcel · Offline support-case authoring 1.0.2 · Linux Chrome

Send the request. Include the files it needs.

Turn one supported cURL request into a support-case ZIP. Preview the recipient notes, match the required files and review the handoff before exporting.

$0.99 USD · one-time purchase

Local browser app · opening steps

Extract the complete RequestParcel-1.0.2.zip and open app/index.html locally in Linux Chrome. Authoring needs no account, server or internet connection. A recipient needs Python 3.10+ and cURL 7.81+: python3 replay.py validates and previews without sending. Sending is a separate explicit command and can modify the target API. Tested on Ubuntu 22.04.5, Chrome 152, Python 3.10.12 and cURL 7.81.0.

Download: ZIP with the described tool and instructions. Check compatibility & limits.

See it in useBuy download — $0.99

No subscription. Final total and tax appear at checkout.

Inspect the workflow before buying

Manual, screenshots and fictional cURL/report/server example. The working authoring app and recipient packet generation are in the paid download. Read the supported syntax and privacy limits first.

  • Read the recipient notes: Preview the request, files, hashes and notes with the same formatter used by the exported README.
  • Resolve the next missing input: Follow the export card to an unmatched file, recognized credential or pending review step.
  • Preview before sending: Author offline. The recipient validates locally; contacting an API requires a separate explicit command.
Read what the recipient will receive. The recipient notes preview shows the request, ordered multipart fields, attachment names and hashes, and expected-versus-observed notes. It uses the same formatter as the exported README.
The recipient notes preview shows the request, ordered multipart fields, attachment names and hashes, and expected-versus-observed notes. It uses the same formatter as the exported README. View full size

See it in use

Replay a fictional multipart upload locally

A screenshot walkthrough with fictional practice data. Select a step to explore.

1. Start with

Replay a fictional multipart upload locally

The fictional case has a 65-byte report payload and two ordered multipart parts.

Sample files and contents

The fictional CASE-001 report has 65 bytes. One POST to the loopback /upload endpoint contains document=@report.txt;type=text/plain and metadata={"mode":"strict"};type=application/json. The 17-byte metadata value is not customer data.

Practice files and guides are free. The complete app is included only where the product page says so.

2. In the app

RequestParcel fictional upload with JSON metadata and the same 65-byte report attachment.
The authoring app shows the ordered multipart parts. Expected and observed notes on this screen are authored example text; measured HTTP statuses are shown in the result tab. Enlarge image ↗

Try it in three steps

  1. Inspect the request and recipient notes without sending it.
  2. Replay locally, then explicitly send to the loopback test server.
  3. Change only the metadata media type and compare server responses.
Show every click and setting
  1. Load the built-in example, inspect the two ordered parts and matched report, read the recipient notes preview, confirm review and export.
  2. Extract the packet into a fresh empty folder and run python3 replay.py; no request is sent. Start the separately included example server from its own folder.
  3. Explicitly send the packet to http://127.0.0.1:8765 and observe 200.
  4. Create a second packet changing only the metadata media type to text/plain; explicitly send that packet to observe 415.

3. The result

Inspect the result

With the same 65-byte file, the local server returned HTTP 200 for JSON metadata and HTTP 415 for text metadata. Both packets passed offline integrity preview.

Observed using the delivered RequestParcel 1.0.2 runner and its loopback demo server. Only the metadata part type changed. No external API was contacted.
Metadata typeServer response
application/jsonHTTP 200
text/plainHTTP 415
What to check in the practice result

The supported request semantics, multipart order and attachment bytes are preserved. The fictional server returns HTTP 200 with application/json metadata and HTTP 415 with text/plain metadata. The runner prints status, discards the response body and preserves source attachments. This controlled demonstration does not establish reproduction against another API.

A fictional loopback test. report.txt is the uploaded input; the result table records actual runner statuses. Preview does not send; sending requires an explicit action.

What it helps you do

For API support engineers sharing an upload case outside their API workspace. Match each file explicitly, inspect supported headers and multipart fields, replace selected whole-header credentials with runtime prompts, and add expected-versus-observed notes. The recipient gets the case, files, hash inventory and Python/cURL runner without needing the authoring app. Save a reviewed JSON project to reopen the case.

What is in your download

  • RequestParcel 1.0.2 local authoring app with source, licence and preserved historical correction notes.
  • Illustrated English HTML manual, four actual screenshots and a fictional upload example with a separate loopback server.
  • Recipient ZIP export with case.json, selected file bytes, SHA-256 inventory, readable HTML/Markdown notes and replay.py.
  • Reviewed JSON project save/reopen, reproducible archive builder and parser/project regression checks. One-time purchase; recipients do not need the authoring app.

Before you buy

  • Author: Linux Chrome, with the entire buyer ZIP extracted. Open app/index.html; no runtime install, server or sign-in is required.
  • Recipient: Linux, Python 3.10+ and cURL 7.81+. Tested with Ubuntu 22.04.5, Chrome 152, Python 3.10.12 and cURL 7.81.0. Other platforms remain unverified.
  • One supported POSIX-style cURL command, explicitly selected attachments, and permission to share those files. A terminal is required for recipient execution and any runtime credential prompt.

Extract the complete RequestParcel-1.0.2.zip and open app/index.html locally in Linux Chrome. Authoring needs no account, server or internet connection. A recipient needs Python 3.10+ and cURL 7.81+: python3 replay.py validates and previews without sending. Sending is a separate explicit command and can modify the target API. Tested on Ubuntu 22.04.5, Chrome 152, Python 3.10.12 and cURL 7.81.0.

Compatibility & limits

One command per case, using a strict POSIX-style cURL subset. Unsupported syntax blocks. Up to 20 files, 10 MiB each and 50 MiB combined; command limit 64 KiB. File multipart parts need an explicit media type. Review query values, bodies, filenames, notes and file contents yourself: secret removal is not guaranteed. Sending uses an exact allowed origin, a 10-second timeout and no redirects or retries; inherited proxies and .curlrc are disabled. Linux is the tested platform. No raw-wire fidelity, cloud upload, arbitrary shell execution or response-body archive. Extract recipient packets into an empty folder; extra files and directories are refused before preview or send.

Get RequestParcel

Perpetual use of the purchased version on your devices for personal or internal commercial work. Keep reasonable backups and modify your own copy; do not redistribute or resell original proprietary code. Third-party licenses and any existing preview permissions retain their rights.

Before payment, save the private recovery code shown by checkout. After Paddle confirms payment, use it to download your ZIP or return for it later. No subscription, future update or email delivery is promised. See the illustrated steps.

License · Terms · Privacy · Refunds · Support

$0.99 USD · once

Buy download — $0.99