Use case 01
Use API when the team needs developer integration without losing the same campaign memory that powers the rest of the platform.
Utility / API
Developer access for Hadogen generation routes, model discovery, and production integration.
API is the developer-facing route for teams connecting Hadogen generation, model catalog data, status checks, and delivery workflows into their own products or internal tools.
API tied back to the active campaign
Generation endpoints visible enough to review clearly
API routes + catalog access packaged as part of the same release flow
Operational reliability kept inside the operating loop
Primary fit
Developer integration
Core control
Generation endpoints
Deliverables
API routes + catalog access
Use cases
What teams actually use this route for.
These pages are now filled as operating surfaces, not placeholders, so each route explains where it fits inside the wider Hadogen workflow.
Use case 02
API is strongest when generation endpoints needs to stay visible and repeatable across more than one launch or format.
Use case 03
The route makes the most sense when api routes + catalog access should move directly into operational reliability and then into a broader Hadogen release package.
Route sequence
The route is structured around concrete operating moves.
This is the sequence teams typically follow when they use this route as part of a broader campaign system.
01
Start from the developer integration need
Use API when the team needs developer integration but still wants the route attached to the same campaign spine and decision history.
02
Use generation endpoints as the main lever
The route is structured around generation endpoints, which helps teams move from direction into api routes + catalog access without dropping context.
03
Close the loop through operational reliability
The final step is not just generation. API stays valuable because operational reliability remains visible inside the same release cycle.
How it works
The route is broken into modules that map to real production decisions.
Each module explains what this lane controls, where it fits, and how it connects to the wider Hadogen system.
01
Where the route fits
API fits teams working on developer integration. The route becomes more valuable when that job stays tied to the same campaign context as the rest of Hadogen.
02
What the route actually controls
API is built around generation endpoints. That focus keeps the output narrower and more repeatable than a general-purpose generator surface.
03
How the route moves forward
API should end in api routes + catalog access, then feed directly into operational reliability and the wider campaign system instead of stopping as a disconnected draft.
Related routes
Move deeper through the platform without leaving the same campaign logic.
FAQ
Questions teams usually ask before they use this route.
Who should use API?
API is built for teams focused on developer integration who still want that work attached to the same campaign operating layer as briefs, references, review, and delivery.
What does API control inside Hadogen?
The route is mainly about generation endpoints. That is the main lever it gives operators while still pushing toward api routes + catalog access.
What should teams open after API?
Most teams move from API into Craft once api routes + catalog access is ready for operational reliability or for the next step in the release cycle.