Skip to content

PayloadStash user guide

PayloadStash workflow from YAML and secret injection through HTTP and AMQP to captures, reports, and secret redaction

PayloadStash turns declarative YAML into a repeatable HTTP and AMQP test suite. Each request or message becomes an executable test case: inject secrets, exercise the target system, carry captured values between operations, verify behavior with reusable expectations, and return an automation-friendly pass or fail result. Deterministic reports and response artifacts preserve the evidence from every run.

Choose an installation Build a test suite

Why PayloadStash

  • A test suite for HTTP and AMQP

    Exercise APIs, brokers, and integrated systems from one YAML suite. Expectations determine the final process status for local testing or automation.

    Build a test suite

  • Secrets enter before transport

    Inject values from a separate secrets file while redacting loaded values from resolved configuration and run logs.

    Handle secrets

  • Capture, verify, and continue

    Test stateful behavior by carrying response values into later requests and asserting status, data, headers, timing, and AMQP outcomes.

    Capture values ยท Verify results

  • Evidence after every run

    Retain resolved YAML, response bodies, CSV results, detailed logs, and a readable Markdown report.

    Inspect run artifacts

  • Container and offline ready

    Use a GitHub Release, UV-managed installation, GHCR image, or packaged air-gapped Docker workflow.

    Choose an installation

Find what you need

  • Install PayloadStash


    Compare GitHub Release, local, cloned, Git-based UV, and Docker installation paths.

    Installation options

  • Run your first stash


    Build and run an HTTP or AMQP test suite, then inspect its pass or fail result and retained evidence.

    Getting started

  • Configure requests


    Define HTTP or AMQP operations, dynamic values, captures, and expectations.

    Configuration guides

  • Solve a problem


    Diagnose installation, configuration, connection, and output issues.

    Troubleshooting

Looking for developer documentation?

Source development, architecture, testing, and packaging documentation remain in the GitHub repository.