■ REST API

Create catalog creatives from your own code.

The same endpoints our MCP server uses: find templates, validate rows, run batches and fetch the results, authenticated with an API key.

Base URLhttps://app.kalpana.one/api/agent/v1

Workflow

Four calls from rows to creatives.

Authentication

Create a key under Settings, API keys. Every call is checked against your role in the workspace it touches.

curl https://app.kalpana.one/api/agent/v1/templates?query=sale -H "x-api-key: sk-your-key"

Method	Endpoint	What it does
GET	/workspaces	Workspaces you can reach, with your role.
GET	/templates	Search templates by name, topic, size or animation.
GET	/templates/{id}/inputs	Fields a template needs, with types and examples.
GET	/asset-collections	Image collections in a workspace.
GET	/assets	Search images by collection or file name.
POST	/batches/validate	Check rows against a template before spending credits.
POST	/batches	Create render jobs from validated rows.
POST	/batches/{batchId}/run	Start rendering. Uses credits.
GET	/batches	List batches and their status.
GET	/batches/{batchId}	Status and counts for one batch.
GET	/batches/{batchId}/outputs	Finished creatives with download links.

Open Settings, then API keys, in the Kalpana app and create a key. Send it in the x-api-key header.

Yes. API keys are limited to 100 requests a minute, and request bodies to 1 MB of JSON.

Yes. The MCP server is a thin layer over these endpoints, so anything an agent can do, your code can do.

Not yet. You can call the API from their HTTP request steps today.

Ready when your catalog is

Import a Figma frame, connect your catalog and preview every row before you spend a credit.