Use case · Image API

Your carousels, published every day, without opening a design tool.

Turn any data source into Instagram carousels: one slide template, one API call per slide, and your scheduler posts the result. This is the pipeline we run for our own accounts.

I want the tool Read the step-by-step guide

Rendered by the API

Six slides, six API calls, zero design sessions

A real carousel, rendered from one template and a six-item JSON file by the script in the guide. Scroll it like you would on your phone.

Cover slide: 5 things nobody tells you before moving to Malta

Slide 3: Register before the three-month mark

Slide 4: Nobody is on time. Not even the bus.

The pipeline

From data to published carousel in four steps

No carousel button, no magic: a template, a loop, a scheduler. Which is exactly why it runs every day.

1
Start from your data

An article, a row in a spreadsheet, a JSON file — anything that gives you a title and a few lines of text per slide. That is the whole input.
2
Design one slide template

Build it in the editor, or describe it and let the authoring agent write it for you. Every text block is a named layer the API can replace: kicker, title, body, slide counter. 1080×1350 or 1080×1080, your call.
3
Render one image per slide

One API call per slide, with that slide's text. Six slides, six calls, six images back — PNG, JPEG or WebP. A short script does the loop.
4
Hand the images to your scheduler

Nadia, or any tool that takes a set of images and posts a carousel on a date. TemplateFox renders; your scheduler publishes.

Step 3, for real

One request per slide

Each call names the layers to change and the text to put in them. The response is the image. The full loop, in Python, is in the guide.

curl

curl -X POST https://api.templatefox.com/v1/image/create \
  -H "x-api-key: sk_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "template_id": "your-template-id",
    "format": "png",
    "modifications": [
      { "name": "kicker",  "text": "1 · Rent" },
      { "name": "title",   "text": "Rent is the first shock" },
      { "name": "body",    "text": "Sliema and St Julian’s cost the most…" },
      { "name": "counter", "text": "2 / 6" }
    ]
  }'

Node.js · @templatefox/sdk

import { Configuration, ImageApi } from "@templatefox/sdk";

const api = new ImageApi(new Configuration({ apiKey: "sk_your_api_key" }));

// One call per slide — loop over your slides array.
const slide = await api.createImage({
  templateId: "your-template-id",
  format: "png",
  modifications: [
    { name: "kicker", text: "1 · Rent" },
    { name: "title", text: "Rent is the first shock" },
    { name: "counter", text: "2 / 6" },
  ],
});
console.log(slide.url);

Also available in Python, PHP, Ruby, Go, Java and C# — see the SDK docs.

Questions people ask

Do I have to design every slide by hand?

No. You design one slide once. Each slide of each carousel then reuses it with different text — the title, the body, the slide number. Change the template and every future carousel picks it up.

Does TemplateFox post the carousel to Instagram for me?

No. TemplateFox makes the images. Publishing is the job of your scheduling tool — Nadia is the one we use, but any tool that accepts a set of images and a date works. The guide shows the hand-off.

Where does the text of the slides come from?

Wherever your content already lives: a blog post you cut into slides, a spreadsheet with one row per carousel, a draft written by an AI assistant. As long as it ends up as a short list of titles and paragraphs, it can become a carousel.

How much does it cost?

One credit per slide. A six-slide carousel costs six credits. The free plan includes 60 renders a month — ten carousels — and paid plans start on the pricing page.

Coming next

Want this as a ready-made tool?

Today the pipeline runs through the API and the guide above. We are measuring who wants a packaged version: paste your content, pick a template, get the carousel scheduled. Leave your email and you will be the first to know.