For Agents
Render templated images at scale by supplying parameters to Duply templates. Useful for personalised social cards, ad creative, and bulk visual content jobs.
Get started with Duply API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"generate a templated image from parameters"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Duply API API.
List available design templates via GET /templates
Render a single image from a template via POST /generate
Render an image using URL-encoded parameters via POST /generate/url
Run a bulk render job via POST /batch and track it via GET /batch/{batchId}
List historical renders via GET /renders and download or delete a specific render
GET STARTED
Use for: I need to render an Open Graph image for a blog post, Generate 500 personalised ad images from a CSV, List all design templates in our Duply account, Upload a new logo asset to use in renders
Not supported: Does not handle template design, image hosting outside Duply renders, or video editing beyond template substitution — use for templated image generation and batch rendering only.
Jentic publishes the only available OpenAPI document for Duply API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Duply API, keeping it validated and agent-ready. Duply is a templated image and video generation service that turns design templates plus dynamic parameters into rendered assets, with batch support and ready-made integrations to Zapier and Make. The API exposes 13 endpoints across templates, generation (single and URL-parameter), batch jobs, render history, and asset uploads. Authentication uses an API key passed in the Authorization header.
Upload reusable assets like logos or fonts via POST /assets
Manage the asset library via GET /assets, GET /assets/{assetId}, and DELETE /assets/{assetId}
Patterns agents use Duply API API for, with concrete tasks.
★ Personalised Open Graph Images per Blog Post
Auto-generate a unique Open Graph image for each blog post or product page by populating a Duply template with the title, author, and accent colour. POST /generate returns a hosted image URL the agent stores against the post, so social shares always show on-brand creative without designer involvement.
POST /generate with template_id, layers={title:'New Post', author:'Sophie'}, store the returned image_url against the blog post record
Bulk Ad Creative from a Spreadsheet
Render hundreds or thousands of personalised ad images from a single template plus a row-per-variant data source. POST /batch dispatches the job, and GET /batch/{batchId} returns progress and the URLs for each completed render. This replaces manual design work for outreach, retargeting, and A/B test variants.
POST /batch with template_id and 1000 layer-value rows, then poll GET /batch/{batchId} until status='completed' and download each render URL
Brand-Asset Library for Generation
Maintain a Duply asset library of logos, fonts, and product photos so generated images stay on-brand without re-uploading every time. POST /assets uploads new files and GET /assets lists the library, which an agent can reference by id when calling /generate or /batch. This keeps templates portable and brand changes centralised.
POST /assets with the new logo file, then update each affected template to reference the returned asset_id
Agent-Driven Visual Content Pipeline via Jentic
Wire Duply into agent workflows that draft, render, and publish visual content. Through Jentic the agent searches by intent, loads the schema for /generate or /batch, and executes — the API key in the Authorization header stays in the Jentic vault, not the agent's prompt context.
Search Jentic for 'generate templated image', load the schema for POST /generate, and execute with the template_id and layer values supplied by the parent content workflow
13 endpoints — jentic publishes the only available openapi specification for duply api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/generate
Generate an image from a template
/generate/url
Generate an image using URL parameters
/batch
Start a batch generation job
/batch/{batchId}
Get batch generation status
/templates
List design templates
/assets
Upload a reusable asset
/renders
List historical renders
/generate
Generate an image from a template
/generate/url
Generate an image using URL parameters
/batch
Start a batch generation job
/batch/{batchId}
Get batch generation status
/templates
List design templates
Three things that make agents converge on Jentic-routed access.
Credential isolation
Duply API keys are stored encrypted in the Jentic vault. Agents receive scoped access at execution, so the raw Authorization value never enters the agent's prompt context.
Intent-based discovery
Agents search Jentic by intent (for example 'generate a templated image' or 'run a batch render') and Jentic returns the matching Duply operation with its input schema.
Time to first call
Direct Duply integration: half a day for auth, layer mapping, and batch polling. Through Jentic: under 30 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Bannerbear API
Templated image and video generation with strong batch and webhook support
Choose Bannerbear when the workflow needs webhooks for completion events; choose Duply for tight Zapier and Make integrations and similar template flows
Placid API
Templated graphic generation with a strong design-tool editor
Choose Placid when designers want a richer template editor; choose Duply for batch-heavy rendering pipelines
Creatomate API
Templated video generation that complements Duply's image surface
Pair with Duply when a campaign needs image variants from Duply and matching video variants from Creatomate
Specific to using Duply API API through Jentic.
Why is there no official OpenAPI spec for Duply API?
Duply does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Duply API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Duply API use?
Duply uses an API key passed in the Authorization header. Through Jentic the key is stored in the encrypted vault and injected at execution, so the raw value never enters the agent's prompt context.
Can I generate images at scale with the Duply API?
Yes. POST /batch starts a bulk render job from one template plus many layer-value rows, and GET /batch/{batchId} returns progress and the resulting render URLs.
What are the rate limits for the Duply API?
The OpenAPI spec does not declare rate limits. Plans set per-minute and monthly render quotas in the Duply dashboard; have your agent handle HTTP 429 with exponential backoff.
How do I render a single templated image through Jentic?
Search Jentic for 'generate templated image', load the schema for POST /generate, and execute with template_id plus the layer values you want substituted. Install with pip install jentic.
Can I upload my own logo and fonts to Duply?
Yes. POST /assets uploads a file and returns an asset_id you can reference inside templates so renders stay on-brand. List, retrieve, and delete them under /assets.
/assets
Upload a reusable asset
/renders
List historical renders