Vertical storytelling
A webtoon API for vertical story workflows.
A webtoon API request combines tall output dimensions, serialized page structure, character references, and scene instructions for vertical reading products.
The API generates original assets. It does not provide a catalog of hosted webtoons, chapters, or creator metadata.
Generate a vertical exampleAccount, API key, usage, and billing open on LlamaGen.AI.
Verifiable request
Two-page vertical episode
curl -X POST \
https://api.llamagen.ai/v1/comics/generations \
-H "Authorization: Bearer $LLAMAGEN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"prompt": "A vertical fantasy episode where Mina follows a glowing fox into a subway portal.",
"size": "1024x1792",
"pagination": {
"totalPages": 2,
"panelsPerPage": 4
},
"comicRoles": [
{
"name": "Mina",
"dress": "yellow raincoat",
"referenceImages": [
"https://example.com/mina-front.webp"
]
}
]
}'Structured response
State your application can route
{
"id": "gen_abc123",
"status": "PROCESSED",
"comics": [
{
"page": 0,
"panels": [
{
"panel": 0,
"caption": "Mina steps through the portal.",
"assetUrl": "https://cdn.llamagen.ai/comics/panel-1.webp"
}
]
}
]
}Output evidence
Inspect the visual result and the machine-readable state.
The visual is evidence of the output category. The JSON is what lets an application correlate the generation, render a preview, store assets, and continue the workflow.

Capability and boundary facts
Facts an integration can verify.
Last verified:
- Endpoint
- POST /v1/comics/generations
- Authentication
- Bearer API key
- Lifecycle
- QUEUED → PROCESSING → PROCESSED or FAILED
- Delivery
- Poll by generation ID or use a callback URL
- Vertical format
- Tall canvas plus multi-page pagination
Good fit
Use it when
- Vertical comic apps
- Serialized creator workflows
- Mobile-first visual stories
Wrong fit
Do not use it for
- Reading or indexing published webtoons
- One-shot synchronous rendering
- Unreviewed automated publishing
Production limits
Plan for the boundaries.
- 01Episode pacing, gutters, and mobile reading rhythm require product-side layout review.
- 02Do not combine fixed panel count with pagination in one request.
- 03Generation is asynchronous; production interfaces must handle processing and failure states.
- 04Outputs should be reviewed against product, brand, safety, and print requirements before delivery.
- 05You must have the rights to prompts, photos, scripts, and reference assets submitted to the API.
Authoritative sources
Next step
Move from evidence to a real API request.
LlamaGen provides the playground, API key, usage, billing, and authoritative service documentation.
Generate a vertical example