Architecture Knowledge HubSeries: Firefly Services for developers. Checked against Adobe's developer documentation on September 23, 2026. Endpoints and limits change, so confirm against the linked source before you ship.
What Adobe Firefly Services is
Firefly Services is a set of REST APIs you call from your own code, not a creative app with a login screen. It covers image generation, adaptation, custom model training, and headless Photoshop and InDesign composition, so you can drop generative and creative operations into an existing pipeline instead of a human workflow.
If your architecture treats "Firefly" as a single box, this series is for you.
What this series covers
- 1. Firefly Services is an API suite, not an app — the family of APIs and where each job belongs
- 2. Three things that break Firefly calls before a pixel renders — auth tokens, signed URLs, storage
- 3. Old Firefly samples may call endpoints that are gone — async-only endpoints and model headers
- 4. Four knobs that make Firefly output repeatable — seeds, negative prompts, reference strength
- 5. Three Firefly endpoints for adapting images at scale — Expand, Fill, Similar
- 6. Your custom model trained. Your API can't see it yet. — training and sharing custom models
- 7. Photoshop API v1 reached end of life on August 31 — what moved to v2
- 8. Three questions to ask before Firefly output goes into an ad — training data, indemnification, provenance
Who this is for
Developers and architects wiring Firefly and its sibling APIs (Photoshop, InDesign) into a PIM, DAM, or campaign pipeline, who need the API-level details rather than a creative-tool walkthrough.