Firefly Controlled Async Generation

Overview

Run a current Adobe Firefly image generation job with prompt approval, response-led polling, artifact custody, and cancellation. This workflow produces a reviewable artifact and evidence before any live side effect.

Prerequisites

• Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle.
• Named product, identity, security, data, budget, release, and operations owners appropriate to the scope.
• Synthetic or approved non-production fixtures with secret and content canaries.

Current Contract

Current Firefly asynchronous operations return jobId, statusUrl, and cancelUrl. Follow those returned URLs rather than inventing a jobs route. Model/API versions and supported input-storage domains are mutable; recheck usage notes for the selected operation. Recheck the dated evidence map before relying on mutable product behavior.

Authentication

Acquire OAuth Server-to-Server credentials only after enterprise entitlement and product assignment are proven. Send x-api-key and bearer headers server-side; never expose them to a browser or job record.