Hook redirect

DevKit's hook mode is a reverse tunnel: Orkestia queues webhook deliveries; your laptop reaches out, drains the queue, and replays each event against a local HTTP server. You do not expose localhost to the internet.

provider  →  Orkestia hook queue  →  ltinteg-devkit poll  →  http://localhost:…
                                                      ↘ acknowledge

Run

ltinteg-devkit hook list
ltinteg-devkit hook redirect
# or
ltinteg-devkit hook redirect <redirect-uuid>

Useful flags: --poll-interval (5s), --poll-limit (10, max 100), --forward-timeout (30s), --ack-retries (3), --force-local (ignore a server-supplied forward_url). Stop with Ctrl+C.

Behaviour

• Poll failures are logged and skipped; the next tick retries. The API tracks delivery, so you always poll offset=0.
• Forward failures are not retried locally. DevKit still acknowledges with status 0 and an error so the server can apply its retry policy.
• Acknowledge retries with full jitter (cap 30s).
• Logs are metadata-only — never bodies, headers, or tokens. --verbose adds paths, status codes, and byte counts.

This is what local runner scaling and Slack/GitHub callbacks use during development. Platform hook primitives are described under Platform services.