DynaPictures API

Name: DynaPictures API
Brand: DynaPictures API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage Processingbearer16 EndpointsREST

For Agents

Generate personalised images and PDFs from templates, manage template assets and workspaces, and subscribe to webhooks so agents can fan out variant imagery from one design.

Install Jentic One Beta

Connect the DynaPictures API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DynaPictures 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 DynaPictures API.

Generate a single personalised image by sending variable values to a template UID

Batch-generate images or PDFs in one call to /batch for high-volume rendering

List, retrieve, create, update, and delete workspaces that scope templates and assets

GET STARTED

Start building with DynaPictures API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DynaPictures API for, with concrete tasks.

★ Personalised Marketing Banner Generation

A marketing tool sends recipient name, headline, and product image to a DynaPictures template UID and gets back a personalised banner ready to drop into an email or ad. Because the template stores layout and the API only ships variables per render, a single design backs thousands of unique outputs.

POST to /designs/{uid} with variables {name: 'Jane', headline: 'Welcome', logo: 'https://...'} and store the returned image URL on the campaign send

Bulk PDF Certificate Generation

An events platform calls /batch with a list of attendees, each with their own name and badge URL, and DynaPictures returns a batch of personalised PDF certificates. The batch endpoint plus webhook subscription means the platform doesn't have to long-poll - it triggers the render and waits for a callback.

POST a list of recipients to /batch with the certificate template UID, then handle the webhook callback to attach each PDF to an attendee record

Per-Client Workspace Isolation

An agency creates a separate workspace per client, uploads each client's logo and brand assets into that workspace, and scopes templates so a render only references that client's media. The /workspaces and /media/{workspaceId}/assets endpoints make this isolation programmatic so onboarding a new client is a script, not a manual setup.

POST /workspaces with name 'Acme Co', then POST /media/{workspaceId}/assets to upload the Acme logo, and reference the asset in subsequent /designs/{uid} renders

Agent-Driven Image Personalisation via Jentic

An AI agent producing variant social cards for a campaign asks Jentic for 'generate a personalised image from a DynaPictures template'. Jentic returns the /designs/{uid} operation, the agent supplies the per-recipient variable map, and DynaPictures renders the image - the agent never sees the bearer token directly.

Use Jentic to search 'generate an image from a template', load the operation for /designs/{uid}, and execute it with the campaign's variable map

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for the dynapictures api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/designs/{uid}

Generate a personalised image from a template

POST

/batch

Batch-generate images or PDFs

GET

/templates

List all templates

GET

/templates/{uid}

Get a single template's metadata

GET

/workspaces

List workspaces

POST

/media/{workspaceId}/assets

Upload a media asset to a workspace

POST

/hooks

Subscribe to a webhook

DELETE

/images/{imagePath}

Delete a generated image

POST

/designs/{uid}

Generate a personalised image from a template

POST

/batch

Batch-generate images or PDFs

GET

/templates

List all templates

GET

/templates/{uid}

Get a single template's metadata

GET

/workspaces

List workspaces

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The DynaPictures bearer token is stored encrypted in the Jentic vault. Agents receive a scoped execution token; the raw token never appears in agent context or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'generate an image from a template') and Jentic returns the matching DynaPictures operation with its input schema, including the per-template variable shape.

Time to first call

Direct integration: 1-2 days to wire up template variables, batch handling, and webhook callbacks across 16 endpoints. Through Jentic: under 30 minutes - search, load, execute.

FAQs

Specific to using DynaPictures API through Jentic.

Why is there no official OpenAPI spec for the DynaPictures API?

DynaPictures does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the DynaPictures 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 DynaPictures API use?

The API uses bearer token authentication - send your DynaPictures API key as 'Authorization: Bearer <token>'. Through Jentic, the bearer token is held in the vault and the agent receives a scoped execution token instead, so the raw key never enters agent context.

Can I generate a PDF with the DynaPictures API?

Yes. POST /batch supports both image and PDF outputs depending on the template configuration - the batch payload specifies the output format per template UID. The single-image endpoint /designs/{uid} returns image renders only.

What are the rate limits for the DynaPictures API?

The OpenAPI spec does not declare a numeric rate limit. DynaPictures applies plan-based monthly render quotas and per-account concurrency caps - for high-volume runs use /batch and subscribe a webhook via /hooks rather than polling.

How do I generate a personalised image through Jentic?

Run pip install jentic, search for 'generate an image from a DynaPictures template', load the operation for POST /designs/{uid}, then execute it with the template UID and a variable map matching the template's named layers. The response contains the rendered image URL.

Can I subscribe to webhook events for render completion?

Yes. POST /hooks subscribes to webhook callbacks; DELETE /hooks unsubscribes. This is the recommended pattern for batch renders - the webhook fires once a batch finishes so callers don't have to poll for individual image URLs.

DynaPictures API

Connect the DynaPictures API to your agent

Capabilities

Start building with DynaPictures API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs