AI — image & videoOAuth server-to-server (Client ID + Client secret)Confirm pricing before publishing
Adobe Firefly Services
Commercially safe Firefly image generation.
AProvider definition
- Provider
- Adobe Firefly Services
- What it does
- Commercially safe Firefly image generation (enterprise Firefly Services credentials).
- Why we need it
- Commercially safe Firefly image generation.
- Used in
- Studio → Images
- AI capabilities
- image, video
- Official site
- https://developer.adobe.com/firefly-services/docs/
BAccount requirements
- Account type
- Adobe enterprise organisation with Firefly Services entitlement
- Prerequisites
- Adobe Admin Console access
- Firefly Services enabled for the org
CConnection method
- Authentication
- OAuth server-to-server (Client ID + Client secret)
- Where to enter it
- Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
- Platform-wide (Super Admin): Super Admin → Platform → IntegrationsPlatform owner. Used for every customer who hasn't added their own key; can also be set as PLATFORM_KEY_<PROVIDER> on the API server.
Setup steps
- 1Sign in to the provider console and open Adobe Developer Console → your project → Firefly Services credential.
- 2Create a new API key. Give it a name such as “SocialMati production”.
- 3Copy the key immediately — most providers show it only once.
- 4Add billing or credits on the provider account if your plan needs it.
- 5Paste the key in the application (see “Where to enter it”), save, then click Test.
DPermissions & API scopes
Scopes are granted on the provider's side when you authorise the app.
This list is generated from the scopes the application's code requests.
EFree vs paid
- Free account / free API access
- No public free tier for Firefly Services.
- Card or billing account required?
- Enterprise agreement.
- Paid plan / costs
- Enterprise Firefly Services contract.
- Quota and usage limits
- Provider-specific rate limits.
Not yet verified. Confirm on the provider's official pricing page before publishing.
FSetup screenshots
Capture each step with real values masked. Save images as public/docs/integrations/adobe_firefly/1.png … 10.png and they appear here automatically.
- Screenshot to add1. Account login / creationThe provider's sign-in or sign-up page.
- Screenshot to add2. Developer consoleThe developer console or dashboard home.
- Screenshot to add3. Project / app creationCreating the app or project used for this integration.
- Screenshot to add4. API enablementThe API or product enabled for the project.
- Screenshot to add5. OAuth configurationConsent screen / OAuth settings with the redirect URIs.
- Screenshot to add6. API key / credentials creationCreating the key, secret or token (mask the value).
- Screenshot to add7. Permissions / scopesThe scopes or permissions requested or approved.
- Screenshot to add8. Billing / quota settingsBilling, credits or quota page.
- Screenshot to add9. Application connectionThe provider card in our application with fields filled (secrets masked).
- Screenshot to add10. Successful connectionThe green Test result or the connected account listed.
GApplication configuration
Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.
| Field | Required | Example / default | Notes |
|---|---|---|---|
| Client ID | Yes | — | |
| Client secret | Yes | •••••••• | Stored encrypted; shown masked after saving. |
HTesting
- 1Click Test — it requests a Firefly Services access token.
- 2Generate a short piece of content in AI Studio with this provider's model selected (Model selector → choose a model from this provider).
ITroubleshooting
| Problem | What to do |
|---|---|
| 401 / invalid API key | The key was revoked, mistyped or belongs to another project. Create a new key and paste it again. |
| 402 / insufficient credits / quota exceeded | Add credits or raise the spending limit on the provider account. |
| “No text model is available” | The provider is switched off or limited to certain plans in Super Admin → AI Management, or its models are disabled. The error message names the cause. |
| Invalid credentials | Check the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure. |
| Missing permissions | Reconnect and accept every permission on the consent screen. If a permission is missing from the list, add it to the app (and get it approved). |
| OAuth failure | Sign-in was cancelled, the app is in development/testing mode, or the user isn't allowed to use it yet. Add the user as a tester or publish the app. |
| Redirect URI mismatch | Copy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings. |
| API not enabled | Enable the API/product for the project or app in the provider console and wait a few minutes. |
| Quota exceeded | Wait for the quota window to reset (see section E) or request a higher quota / add credits. |
| Account not eligible | Check the account requirements in section B (e.g. business/professional account, verified property, registered organisation). |
| App review required | Permissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions. |
| Billing required | Add a payment method or prepaid credits on the provider account (see section E). |
JDisconnect & security
- Revoke access at the provider
- Delete the key in the provider console, then remove it from the provider card in the application.
- Disconnect in the application
- App → Integrations → Providers & API keys or Super Admin → Platform → Integrations → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
- Rotate credentials
- Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
- How credentials are stored
- Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
- What data the application can access
- Only the prompts and files you send for generation. Requests are sent from our server; the key is never exposed to the browser.

