adobe-known-pitfalls

# Adobe Known Pitfalls ## Overview The 10 most common mistakes when integrating with Adobe APIs, based on real production issues. Each pitfall includes the anti-pattern, why it fails, and the correct approach. ## Prerequisites - Access to your Adobe integration codebase - Understanding of Adobe API architecture (OAuth, async jobs, rate limits) ## Instructions ### Pitfall 1: Still Using JWT (Service Account) Credentials **Status: CRITICAL** — JWT credentials reached End of Life June 2025. ```typescript // WRONG: JWT auth (no longer works as of 2025) import jwt from 'jsonwebtoken'; import fs from 'fs'; const privateKey = fs.readFileSync('private.key'); const jwtToken = jwt.sign({ exp: Math.round(Date.now() / 1000) + 86400, iss: orgId, sub: technicalAccountId, aud: `https://ims-na1.adobelogin.com/c/${clientId}`, }, privateKey, { algorithm: 'RS256' }); // RIGHT: OAuth Server-to-Server (current standard) const res = await fetch('https://ims-na1.adobelogin.com/ims/token/v3', { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, body: new URLSearchParams({ client_id: process.env.ADOBE_CLIENT_ID!, client_secret: process.env.ADOBE_CLIENT_SECRET!, grant_type: 'client_credentials', scope: process.env.ADOBE_SCOPES!, }), }); ``` --- ### Pitfall 2: Not Caching IMS Access Tokens IMS tokens are valid for 24 hours. Generating a new token per request wastes 200-500ms: ```typescript // WRONG: New token every request (20...