How I used Claude AI to build a ready to import Postman Collection for Adobe Journey Optimizer (AJO)

ADOBE JOURNEY OPTIMIZER (AJO)

Pradeep Jaiswal

4/21/20262 min read

While Adobe Experience Platform (AEP) offers ready-to-import Postman collection, Adobe Journey Optimizer (AJO) currently lacks a similar official resource. This leaves Solution Architects like myself or Data Engineer stuck in the manual, tedious cycle of copying endpoints and schemas from documentation - a process that is as time-consuming as it is prone to error.

Recently, while chatting with my professional network, “Andrew Robert” shared the brilliant idea of using AI to automate this entire workflow. The goal was simple: provide the AI with the official Adobe Developer documentation URLs and ask it to generate a fully functional, importable Postman JSON collection.

Press enter or click to view image in full size

The Result: Adobe AJO ready to import Postman Collection

The AI successfully scraped the documentation and generated a collection featuring 52 requests organized into 10 top-level folders. Key highlights of the generated collection include:

Automated Authentication: A built-in OAuth S2S token generation script that auto stores the ACCESS_TOKEN for subsequent calls.

Logical Grouping: Folders mirror the official Adobe navigation (e.g., Journey Capping, Triggered Campaigns, Content Templates).

Variable Support: Placeholders for all environment-specific data, making it “plug-and play.”

I have uploaded the API file here for ready to import into Postman :

https://github.com/pradyjswl/Adobe-Journey-Optimizer-API-Collection

The Challenge: The Complexity of AJO APIs

The Adobe Journey Optimizer API suite isn’t just a handful of endpoints. It covers a wide range of functionalities:

Journey Management: Listing, detailing, and versioning journeys.

Capping & Throttling: Complex rules to manage API load and frequency.

Orchestration & Triggering: Moving data through datasets and triggering specific campaigns.

Content Management: Managing fragments, templates, and suppression lists.

Manually creating a Postman collection for over 50 endpoints , complete with variables for CLIENT_SECRET, API_KEY, and SANDBOX_NAME is a prime candidate for automation.

The Solution: Leveraging AI Scraping

Using Claude, I provided a detailed prompt acting as an API documentation Specialist. I directed it to the official Adobe Developer site with a specific instruction: navigate through the references, extract endpoint paths, HTTP methods, and body schemas, specifications where available.

Here is the screenshot of my chat with Claude

At Shiftlytic, we specialize in advanced Adobe Journey Optimizer (AJO) architecture, helping global brands bridge the gap between their complex data ecosystems and actionable engagement. Don’t let manual setup hold back your engineering velocity.

Contact us today to schedule one free consultation. Let’s optimize your AJO integration and ensure your data architecture is accurate, scalable, and fully automated.

Get in Touch