Imagior API
Agent-ready OpenAPI document · curated by JenticMediaImage ProcessingapiKey5 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Render branded images from pre-designed templates by supplying per-element overrides such as headline text, background images, or button colors.
Use for: I want to render an Open Graph image from a Figma-style template, Generate a YouTube thumbnail with custom title text, Produce a personalised email banner for a customer, List all templates I have created in Imagior
Not supported: Does not handle image hosting, CDN delivery, or video rendering - use for templated image generation with per-element overrides only.
Jentic publishes the only available OpenAPI specification for Imagior API, keeping it validated and agent-ready. Imagior generates images from design templates with per-element modifications. A user designs a template once in the Imagior UI, then the API renders that template with overrides such as text, colors, or image swaps to produce a final image. The API exposes template listings, element discovery, image generation, and account usage so a marketing or e-commerce stack can produce branded visuals at scale.
Install Jentic One Beta
Connect the Imagior API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Imagior API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fimagior.com%2Fimagior" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fimagior.com%2Fimagior" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Imagior API.
List all design templates available in the connected account
Inspect a template's basic elements before generating an image
Inspect a template's full element list including text and image layers
Generate a final image by supplying element overrides for a chosen template
Check account-level usage and remaining generation quota
Use Cases
Patterns agents use Imagior API for, with concrete tasks.
★ Templated Marketing Image Generation
Marketing teams design a hero or banner template once, then call /api/image-generate with overrides like headline, subhead, and product photo to produce dozens of variants. This removes the back-and-forth with design for routine asset production while keeping brand consistency through the locked template.
GET /api/templates to find the banner template, POST /api/image-generate with the template ID and the overrides for the headline and product image, then store the returned image URL.
Open Graph and Social Card Rendering
Blogs and SaaS docs sites need Open Graph images per article. Calling /api/image-generate with the article title, author, and category as element overrides produces a per-article social card without designer involvement. The same template can power Twitter cards and LinkedIn previews from a single source of truth.
On each article publish, POST /api/image-generate with the OG template ID and the article title, then write the returned image URL to the OG meta tag.
Personalised Customer Communications
Lifecycle emails and in-app messages perform better with a name or plan-specific banner. Looping over a customer list and generating a per-customer image via Imagior produces a unique asset per recipient. A template owner can change the design centrally and every future email picks up the change automatically.
For each customer, POST /api/image-generate with overrides for first name and plan tier, then attach the returned image URL to the outgoing email.
Agent-Driven Visual Content
An AI agent that drafts blog posts or social updates can call Imagior to generate the accompanying visual. The agent first asks Jentic to discover the template's elements, then runs /api/image-generate with the inferred overrides. Jentic keeps the API key in the vault so the agent never holds the secret.
Search Jentic for 'generate an image from an Imagior template', load the schema, and execute with the template ID and the agent's chosen element overrides.
Key Endpoints
5 endpoints — jentic publishes the only available openapi specification for imagior api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/api/image-generate
Generate an image from a template with overrides
GET
/api/templates
List design templates
GET
/api/templates/{id}/elements
List all elements on a template
GET
/api/templates/{id}/elements/basic
List basic elements on a template
GET
/api/account
Get account usage and remaining quota
POST
/api/image-generate
Generate an image from a template with overrides
GET
/api/templates
List design templates
GET
/api/templates/{id}/elements
List all elements on a template
GET
/api/templates/{id}/elements/basic
List basic elements on a template
GET
/api/account
Get account usage and remaining quota
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Imagior by hand means setting up its API key in an Authorization header against api.imagior.com and discovering template elements before overriding them yourself. Through Jentic you install once, import the Imagior API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Imagior takes the generation inputs in the request body and exposes templates through read paths, so scope the agent to the operations it needs, such as listing templates, reading their elements, and generating an image. Because you choose the allowed operations, an agent limited to reading templates never gets the generate operation unless you add it.
Credential isolation
Your Imagior API key is stored once, encrypted, by your own Jentic One instance and injected into the request header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'generate a branded image', and Jentic returns the image-generate operation along with the template-element read operations and their schemas so the agent wires overrides correctly without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Imagior API through Jentic.
Why is there no official OpenAPI spec for Imagior API?
Imagior does not publish a canonical OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Imagior via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Imagior API use?
The API uses an API key sent in a request header (apiKeyAuth). Through Jentic the key is held in the encrypted vault and injected at execute time, so it never appears in the agent's prompt or logs.
Can I generate an image with custom headline text?
Yes. POST /api/image-generate with the template ID and an overrides payload that targets the text element discovered via GET /api/templates/{id}/elements. Imagior renders the final image with the new text in the original style.
How do I find which elements a template exposes for overrides?
GET /api/templates/{id}/elements returns the full element list including text and image layers, while GET /api/templates/{id}/elements/basic returns the simplified set most commonly overridden.
How do I generate an image through Jentic?
Run pip install jentic, search for 'generate an image from an Imagior template', load the /api/image-generate schema, and execute with the template ID and overrides. The returned URL points at the rendered image.
How do I check my remaining Imagior quota?
GET /api/account returns account-level usage and the remaining generation count for the current period, which is useful for batch-job back-pressure.
Can I limit what my agent is allowed to do with the Imagior API?
Yes. Because Jentic One is self-hosted and you set the rules, you decide which Imagior operations the agent may call, so you can grant only what a task needs, such as listing templates with GET /api/templates and reading their elements with GET /api/templates/{id}/elements. An agent scoped to those read operations cannot run POST /api/image-generate or check quota with GET /api/account unless you add those operations. Your Imagior API key stays with your own instance and is injected at execution time, so a narrowed agent never sees the credential or the operations you withheld.
GET STARTED