Update Template Modifications
Update text and image content in template layers
Enterprise Only
This endpoint is available only to first party clients like the Orshot MCP server and workspaces on the Enterprise plan. Checkout the Enterprise Pricing to get access.
Update the content of text and image layers in a studio template. This endpoint allows you to modify parameterized elements directly without re-saving the entire template structure. Supports updating multiple parameters across multiple pages in a single request.
For detailed information about the template data structure, see Anatomy of a Template.
Endpoint#
https://api.orshot.com/v1/studio/templates/:templateId/update-modificationsQuery Parameters#
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
includeThumbnails | Boolean | No | false | When true, thumbnails are regenerated for the pages that had modifications applied, and the response waits for all renders to complete. When false or absent, thumbnails regenerate asynchronously after the response. |
Request Examples#
// Update text and image on a single page
await fetch("https://api.orshot.com/v1/studio/templates/12345/update-modifications", {
method: "PATCH",
headers: {
"Content-Type": "application/json",
Authorization: "Bearer <ORSHOT_API_KEY>",
},
body: JSON.stringify({
data: [
{
page: 1,
modifications: {
headline: "Flash Sale: 24 Hours Only!",
subtitle: "Don't miss out on amazing deals",
product_image: "https://cdn.example.com/sale-banner.png",
price: "$49.99"
}
}
],
embed_user_id: "your-external-user-id" // Optional
}),
});Rate Limits#
| Limit | Value |
|---|---|
| Requests per minute | 30 |
| Max modifications per request | 50 |
URL Parameters#
| Parameter | Type | Required | Description |
|---|---|---|---|
templateId | Integer | Yes | The ID of the template to update |
Request Body Structure#
The request body uses a data array format, where each item specifies the page number and modifications to apply:
{
"data": [
{
"page": 1,
"modifications": {
"headline": "New Headline Text",
"product_image": "https://cdn.example.com/new-image.png",
"price": "$99.99"
}
}
]
}Request Body Parameters#
| Parameter | Type | Required | Description |
|---|---|---|---|
data | Array | Yes | Array of page modification objects |
embed_user_id | String | No | Assign or update the template's embed user. Accepts either an external user ID (resolved using your workspace's embed configuration) or an Orshot internal ID (prefixed with eui_). |
Data Object Structure#
Each object in the data array should include:
| Field | Type | Required | Description |
|---|---|---|---|
page | Integer | Yes | Page number (1-indexed) to apply modifications to |
modifications | Object | Yes | Key-value pairs of parameterId to new value |
Supported Modification Types#
Text Content#
Update text element content by its parameterId:
{
"page": 1,
"modifications": {
"headline": "Summer Sale 2026!",
"subtitle": "Up to 50% off all items",
"cta_text": "Shop Now"
}
}Image URLs#
Update image sources by providing a URL:
{
"page": 1,
"modifications": {
"product_image": "https://cdn.example.com/product.png",
"logo": "https://cdn.example.com/logo.svg",
"background": "https://cdn.example.com/bg.jpg"
}
}Style Properties#
Update style properties using dot notation:
{
"page": 1,
"modifications": {
"headline.fontSize": 48,
"headline.color": "#ff0000",
"cta_button.backgroundColor": "#007bff",
"subtitle.fontFamily": "Inter"
}
}Response Fields#
| Field | Type | Description |
|---|---|---|
success | Boolean | Whether the operation completed |
template_id | Integer | ID of the updated template |
applied | Array | List of successfully applied modifications |
failed | Array | List of failed modifications (only if any failed) |
thumbnails | Object | Only present when ?includeThumbnails=true. See Thumbnails Object Structure below |
Which array a key lands in#
| Array | Present when | Meaning |
|---|---|---|
applied | always | The value was written to the template |
failed | only when non-empty | The key did not land and you need to change something: unknown parameter, rejected value, ambiguous key |
skipped | only when non-empty | The key is valid for a render but has nothing to store on a template, so there is nothing to fix |
failed and skipped are omitted from the response when they are empty, so a
clean patch returns applied only. Check data.failed before treating a patch
as fully successful.
Applied/Failed Object Structure#
| Field | Type | Description |
|---|---|---|
page | Integer | Page number where the modification was applied/failed. A pageN@ key is reported against the page it addressed, not the page of the enclosing item |
page_id | String | Stable UUID of the page where the modification was applied/failed. null if the requested page number does not exist on the template |
key | String | The parameter ID or style path |
type | String | Type of modification: text, image, video, shape, container, canvas, element, or style |
prop | String | The property that was written, for style items (fontSize, x, width, alt, …). Absent for content items |
content | String | The applied value (only for applied items) |
error | String | Error message (only for failed items) |
reason | String | Stable machine-readable code for the failure, for per-key failures (see below). Absent on item-level failures |
Keys you need to act on come back in failed with a reason code:
| Reason | Meaning |
|---|---|
param_not_found | No element on the template carries that parameter ID |
param_not_parameterizable | The element exists but its parameter is switched off |
invalid_content_value | Value rejected by validation (error carries the specific message) |
non_string_value / invalid_value / invalid_crop_value | The value type does not fit the parameter or property |
render_only_inline | Inline text parameters (headline:name) apply per render; send the whole headline value instead |
bare_content_multi_page | Ambiguous key on a multi-page template; prefix it with pageN@ |
page_not_found | The pageN@ prefix names a page the template does not have |
unsupported_key / unsupported_type / unsupported_element_type | The key or the element type has no stored home for that kind of value |
sanitized_placeholder | The value is a log stand-in for uploaded bytes ([base64 ...]), not real content |
Keys that are legitimate for a render but have no home on a stored template come
back in skipped with a reason and a human-readable message. They are
informational: send them to a render call instead.
| Reason | Meaning |
|---|---|
overridden_by_page_key | A pageN@ key for the same parameter was also sent and won for that page |
render_only_prompt | AI prompt keys (photo.prompt, .promptMode, .promptReferences) |
render_only_transition | Transition dynamics (.showAt, .hideAt, .enter*, .exit*) |
render_only_video | Video dynamics on a video element (.trimStart, .muted, .loop) |
not_persisted_href / not_persisted_contentType | .href and .contentType are read per render, never stored |
Thumbnails Object Structure#
When ?includeThumbnails=true is passed, a PNG thumbnail is regenerated for only the pages that had modifications applied (not all pages). The thumbnails object in the response has this shape:
| Field | Type | Description |
|---|---|---|
success | Boolean | true if at least one page rendered successfully |
pages[].page | Integer | 1-based page number |
pages[].page_id | String | Stable UUID of the page |
pages[].thumbnail_url | String|null | Public URL of the new thumbnail PNG. null if this page failed |
pages[].error | String|null | Error message if this page failed. null on success |
When ?includeThumbnails is not passed, thumbnails regenerate in the background for the modified pages and appear on the template shortly after the response.
Supported Style Properties#
When using dot notation for style updates, the following properties are commonly supported:
| Property | Type | Description |
|---|---|---|
fontSize | Number | Font size in pixels |
fontFamily | String | Font family name |
color | String | Text color (hex, rgb, rgba) |
backgroundColor | String | Background color |
opacity | Number | Opacity (0-1) |
fontWeight | String/Number | Font weight (normal, bold, 100-900) |
textAlign | String | Text alignment (left, center, right) |
letterSpacing | Number | Letter spacing in pixels |
lineHeight | Number | Line height multiplier |
Error Responses#
| Status Code | Error | Description |
|---|---|---|
| 400 | data required | Request body missing data array |
| 400 | data array empty | Empty data array |
| 400 | Maximum 50 total modifications per request | Too many modifications in one request |
| 403 | Access Forbidden | Invalid API key or template not in workspace |
| 404 | Template not found | Template ID doesn't exist |
| 429 | Rate limit exceeded | Too many requests (max 30/min) |
Invalid per-item input (a non-positive page, or modifications that isn't an object) does not fail the request: the item is reported in the failed array and the response still returns 200.
| 500 | Internal server error | Server-side error |
Cache Invalidation#
When modifications are applied:
- Template render cache is automatically invalidated
- Dynamic URL cache for the template is cleared
- Subsequent render requests will use the updated content
Best Practices#
- Use Parameter IDs: Ensure your template has
parameterIdset on elements you want to update - Batch Updates: Combine multiple page modifications in a single request to reduce API calls
- Validate URLs: Ensure image URLs are accessible and return valid images
- Error Handling: Always check the
failedarray in responses for partial failures. It is omitted when every key landed, so testdata.failedbefore reading its length. Keys inskippedneed no action - Style Consistency: When updating styles, ensure values are compatible with the element type
Ready to automate?
Start rendering images, PDFs and videos from your templates in under 2 minutes. Free plan, no credit card.
Get your API key- Image, PDF and video generation via API
- Visual editor with AI and smart layouts
- Zapier, Make, MCP and 50+ integrations
- White-label embed for your own app
- 30 free credits — no credit card required