Runway Polling-to-Event Relay

Overview

The documented Runway generation surface exposes task retrieval and cancellation, not a native generation-completion webhook endpoint. Build notifications by reconciling provider task state into an internal outbox, then deliver idempotent internal events or your own signed customer webhook.

Prerequisites

• Durable operations, provider task IDs, and legal state transitions
• A bounded polling scheduler and transactional outbox
• Consumer authentication, signing, retry, and replay policies

Instructions

Step 1: State the authority boundary

Document that Runway is polled via GET /v1/tasks/<task-id>. Do not configure a fictional provider webhook secret or tell consumers that a callback originated from Runway.

Step 2: Reconcile provider state