Adobe's Developer API — what can we build with it?

Adobe's developer platform crossed my desk this week. I keep my stack tight — a tool earns a slot only when there's a real build that proves it ships faster work, not slower meetings — and Adobe was overdue for a serious look.

Most people know Adobe for the creative tools. I've been around Photoshop since the early aughts, Dreamweaver before that, half a dozen of their products since. The developer side is a different surface entirely: programmable image generation, server-side Photoshop, document automation, e-signature. A lot of it is reachable from outside an enterprise tenant — and more of it earns a slot in the stack than I'd assumed walking in.

What's there

Seven you can wire up today on a free dev account:

1. 01
   FireflyGenerative image

   Text-to-image, generative fill, expand. Commercially safe — trained on Adobe Stock + licensed content. The lawyers-can-sleep alternative to OpenAI's image models.

2. 02
   Express Add-ons SDKIn-canvas React

   React panels that run inside Adobe Express (Adobe's Canva). Distribute via Adobe's marketplace.

3. 03
   Photoshop APIServer-side image ops

   Server-side Photoshop — autoTone, autoCrop, replace a layer, run a .PSD action on an uploaded image.

4. 04
   PDF ServicesPDF operations

   Programmatic PDF: create, OCR, extract text and tables, convert to/from Word/Excel.

5. 05
   PDF EmbedIn-page viewer

   Drop-in PDF viewer with annotations, search, and analytics.

6. 06
   Document GenerationTemplate → PDF

   .docx template + JSON payload → rendered PDF or Word. Mail-merge for the 2020s.

7. 07
   Acrobat SignE-signature

   E-signature, multi-party flows, webhook on completion. The DocuSign analog.

The rest of Adobe's developer surface — AEM, Analytics, Target, Experience Platform, the whole Experience Cloud — sits behind enterprise tenants. Readable, not buildable from outside.

What's the cost

Shipping cost-effectively means knowing where the bill arrives before the build. Across these APIs, the spend lands in four distinct shapes:

Free

$0 · No metering · No bill

PDF Embed · Express Add-ons SDK

The viewer SDK is free outright. Express add-on development is free; distribution through Adobe's marketplace doesn't cost the builder anything — Adobe earns from the Express subscribers your add-on serves.

Free tier

500 doc transactions/mo free · Volume contract beyond

PDF Services · Document Generation

No time limit on the free tier. 1 transaction = up to 50 pages for most operations, or up to 5 pages for Extract / PDF→Markdown. Production volume moves to annual volume-contract pricing, quoted by sales.

Pay-per-credit

$0.02–$0.10 per image · Floor ≈ $1,000/mo for production

Firefly Services · Photoshop API

Free credits to prototype. Volume discounts kick in above 10k credits/month. If you already run on an Adobe VIP or ETLA contract, credits can fold in. This is the API to watch on the budget — volume image generation gets expensive fast.

Subscription

Bundled into Sign Solutions plans · No pay-per-signature

Acrobat Sign API

The API rides whichever Sign tier you're on. Cost is predictable once you're in, but there's no honest pay-as-you-go path; either you're on Sign or you're not.

One project that uses all of it

A freelancer's deal-flow studio. From creative brief to signed contract, one product, every solo-shippable Adobe API on the chain.

The path through:

1. Designer iterates concept imagery inside an Express add-on, generating variations with Firefly.
2. Approved images get polished server-side with the Photoshop API — brand template, output sizes, watermarks.
3. Document Generation renders the polished assets into a proposal from a .docx template + JSON payload.
4. The PDF lives in a client portal, embedded with PDF Embed for inline review and annotation.
5. Acrobat Sign sends the final for signature, webhooks back on completion.
6. PDF Services extracts the structured data — line items, dates, terms — into the database, where it informs the next deal.

The shape is real. Freelancers and small agencies stitch this together today with five different tools and a lot of copy-paste. One studio that runs the whole pipeline on Adobe's own primitives is a category most builders haven't built yet — because most builders haven't taken Adobe's developer side seriously.

What's next

First slice — Express add-on + Firefly + Photoshop API — target by 2026-05-28. Public repo goes live with the next post, when there's actually something to clone.

Update — 2026-05-24

Three days after publishing this, I sat down to spec the first slice and realized I was building portfolio, not product. The deal-flow studio above stitches Adobe's primitives into a workflow that real freelancers already solve with Canva, Notion, and DocuSign — each best-in-class at its station. A re-stack on Adobe APIs is technically interesting, but it doesn't beat the existing tools individually. And Acrobat Sign requires a paid subscription baseline, which kills the free-path story for any end user I'd actually sell to.

The same six primitives unlock a different shape: a personalized print product. Themed photo calendars, holiday cards, baby's-first-year books, wedding albums. The buyer isn't a designer — they pay for pro-looking output from raw photos. Five of the seven APIs map cleanly. Firefly for themed backgrounds and generative fill on awkward photos. Photoshop API for batch auto-tone and smart crop to template slots. Document Generation for the calendar or book layout from a JSON payload. PDF Services for print-ready export. PDF Embed for in-browser preview before the customer pays. Express add-ons and Acrobat Sign drop out — B2C consumers don't use Express, and there's no signature flow.

The front-runner is a memory-books studio — B2C personalized print, with the Q4 photo-calendar spike built into the buying calendar. It earns its slot on Adobe primitives because it's earning a buyer, not a portfolio.

The next post is the spec.