ACTION.md

\description{"Execute an HTTP request and capture the full roundtrip as structured JSON."} \requires{"actionbox"}

Execute an HTTP request against \input{url, required} and capture the full roundtrip as structured JSON written to \output{capture, schemaRef="schemas/capture.json"}.

\input{method, default="GET"} specifies the HTTP method. \input{headers, schemaRef="schemas/headers.json"} is a list of Key: Value headers to include in the request. \input{body} is the request body. \input{timeout, default="30s"} sets the request timeout in Go duration format. \input{follow_redirects, default="true"} controls whether HTTP redirects are followed. \input{insecure, default="false"} skips TLS certificate verification when set.

Routing key injection: When the step has routingContext set (which exposes SIGNADOT_ROUTING_KEY), the action automatically injects routing-key headers across multiple propagation formats — OTel baggage, tracestate, Jaeger, Datadog, and any customHeaders from the cluster's config. No manual header injection at the plan spec level.

Header sanitization: Sensitive headers are removed from the capture output. Request: Cookie, Authorization, Authentication. Response: Set-Cookie. Additional headers can be configured via cluster config.

Body parsing:

• application/json — parsed as structured JSON
• application/x-www-form-urlencoded — parsed as map[string][]string
• Other content types or parse errors — base64-encoded string
• Empty body — null

Response bodies are capped at 200KB.

Exit codes:

• 0 — request completed (inspect the capture JSON for status/error details)
• 1 — usage error (bad flags, file read error, invalid header format)

Output format:

The capture output is a JSON object:

{
  "request": {
    "proto": "HTTP/1.1",
    "method": "GET",
    "uri": "/api/items?page=1",
    "host": "example.com",
    "query": {"page": "1"},
    "message": {
      "startedAt": "2026-03-16T12:34:56Z",
      "headers": {"Accept": "application/json"},
      "body": null
    }
  },
  "response": {
    "statusCode": 200,
    "proto": "HTTP/1.1",
    "message": {
      "startedAt": "2026-03-16T12:34:57Z",
      "finishedAt": "2026-03-16T12:34:57.005Z",
      "headers": {"Content-Type": "application/json"},
      "body": {"items": [{"name": "a"}], "total": 1}
    }
  }
}

On transport error, the response contains an error field instead:

{
  "request": { "..." : "..." },
  "response": {
    "error": "dial tcp: connection refused"
  }
}

set -- --url "$(cat ./context/url)"

[ -f ./context/method ] && set -- "$@" --method "$(cat ./context/method)"
[ -f ./context/timeout ] && set -- "$@" --timeout "$(cat ./context/timeout)"
[ -f ./context/follow_redirects ] && set -- "$@" --follow-redirects="$(cat ./context/follow_redirects)"
[ -f ./context/insecure ] && set -- "$@" --insecure="$(cat ./context/insecure)"
[ -f ./context/body ] && set -- "$@" --body-file ./context/body
[ -f ./context/headers.json ] && set -- "$@" --headers-file ./context/headers.json

actionbox request-http "$@" > ./outputs/capture.json