Okapi Okapi

Adobe Firefly API POST /v1/images/fill endpoint removal

Stopped workingSubscribe to Adobe Firefly APIShare

Calls to POST /v1/images/fill on Adobe Firefly API stopped working on September 10, 2025.


Calls it hits

  • POST /v1/images/fill

What to use instead of these calls

Call POST /v3/images/fill-async and poll the returned statusUrl via GET /v3/status/{jobId} for the result.

In Adobe Firefly API's words

Removed deprecated APIs : The following APIs are no longer available: - Generate Images v2 API - Expand Image v1 API - Fill Image v1 API

Adobe Firefly API, Announcement

Facts

API
Adobe Firefly API firefly-api.adobe.io
Kind
Endpoint removal
Takes effect
September 10, 2025
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Adobe Firefly API's own pages

Questions

When does this change take effect?

Calls to POST /v1/images/fill on Adobe Firefly API stopped working on September 10, 2025.

What happens to calls after September 10, 2025?

They have failed since September 10, 2025.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.


More from Adobe Firefly API 2

  1. POST /v1/images/expandEndpoint removal Stopped working
  2. POST /v2/images/generateEndpoint removal Stopped working

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub

Get notifications

Subscribe to Adobe Firefly API

Hear about each breaking change Adobe Firefly API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Adobe Firefly API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.