Migrate from Placid to Orshot

# Migrate this project from Placid to Orshot

You are helping me move from Placid (api.placid.app) to Orshot (api.orshot.com). Orshot renders images, PDFs and videos from templates through an API, and has native n8n, Make, Zapier, Pipedream and Airtable apps plus an MCP server (https://mcp.orshot.com/mcp, setup at https://orshot.com/agents). If you can connect to that MCP server, do it first: it lets you list my Orshot templates, read their parameters and test renders directly. Read the docs linked below before changing anything, then do the work in the order given.

## 1. Find every Placid touchpoint in this project

Search for, and list with file paths:
- `api.placid.app` (REST: `/api/rest/images`, `/api/rest/pdfs`, `/api/rest/videos`; URL API: `/u/`)
- the `placid` npm/pip package, the Placid WordPress, Shopify or Webflow plugins, or SDK imports
- `PLACID` environment variables and API tokens (Placid tokens are per project)
- template UUIDs (short strings like `ikuscviexl1ry`), `layers` objects keyed by layer name, `pages[]` and `clips[]` arrays
- `polling_url` loops and `webhook_success` handlers that receive Placid image events
- URL API builders (`?title[text]=…&s=SIGNATURE`, HMAC-SHA256 over the query string)
- n8n, Make or Zapier exports in the repo that contain Placid nodes

## 2. Templates

Templates cannot be converted from code alone. I will import each Placid template into Orshot myself (New Template → Placid tab → upload the editor page saved as .mhtml). Guide: https://orshot.com/migrate/from-placid

Once imported, each Placid layer name is an Orshot parameter with the same name ("bg_img" stays `bg_img`, "quote" stays `quote`). Ask me for the Orshot template IDs, or read the parameters with:
- GET /v1/studio/templates/{id}: https://orshot.com/docs/api-reference/studio-template-get
- List templates: https://orshot.com/docs/api-reference/studio-templates-list

Build a mapping table: Placid template UUID → Orshot templateId. Show it to me before editing code.

## 3. Rewrite the API calls

Reference: https://orshot.com/docs/api-reference/render-from-studio-template

Placid:
```http
POST https://api.placid.app/api/rest/images
Authorization: Bearer PLACID_TOKEN
{ "template_uuid": "UUID", "create_now": true, "layers": { "title": { "text": "Hello", "text_color": "#111" }, "photo": { "image": "https://…" } }, "webhook_success": "…" }
```

Orshot:
```http
POST https://api.orshot.com/v1/studio/render
Authorization: Bearer ORSHOT_KEY
{ "templateId": 12345, "modifications": { "title": "Hello", "title.color": "#111", "photo": "https://…" }, "response": { "type": "url", "format": "png" } }
```

Rules:
- `modifications` is a flat object keyed by parameter name. A text layer's `text` and a picture layer's `image` become the value itself.
- Layer properties become dot keys: `text_color` → `"title.color"`, `font` → `"title.fontFamily"`, `background_color` → `"box.backgroundColor"`, `border_color` → `"box.stroke"`, `border_width` → `"box.strokeWidth"`, `border_radius` → `"box.borderRadius"`, `hide: true` → `"title.opacity": 0`, `opacity: 40` → `"title.opacity": 0.4`. Docs: https://orshot.com/docs/dynamic-parameters
- Placid `pages: [{ template_uuid, layers }]` (PDFs) and `clips: [{ template_uuid, layers }]` (videos) become pages of one Orshot template with page-prefixed keys: `"page2@title"`. Keys without a prefix apply to every page. I will combine the imported templates into one multi-page template in the Studio; ask me for its ID.
- `response.format`: png, jpg, webp, avif, pdf, mp4, webm, gif. Placid's `modifications.image_format` maps to it. `response.type`: url, base64, binary. `modifications.filename` → `response.fileName` (no extension).
- PDFs: `modifications.dpi` and `color_mode` → `pdfOptions: { dpi, colorMode }`. Docs: https://orshot.com/docs/pdf-generation/pdf-options
- Video: `modifications.fps` → `videoOptions: { fps }`. Clip audio is set on the page in the Studio, not per request. One credit per second, the same as Placid. Docs: https://orshot.com/docs/video-generation/video-options
- Orshot is synchronous by default: the response contains `data.content` (the file URL or data). Remove `create_now` and any `polling_url` loops.
- If the code relies on `webhook_success`, use async mode instead: add `"mode": "async"` inside `response`, plus top-level `webhook_url` and `metadata` (Placid's `passthrough`, up to 1024 characters). You get `202 { id, status: "queued" }`; the webhook body is `{ event: "render_job.finished", job }`; or poll GET /v1/studio/render-jobs/{id}. Docs: https://orshot.com/docs/api-reference/async-render-start
- `modifications.width`/`height` have no equivalent: Orshot renders at the template size; use `response.size` (Smart Resize) for other sizes. `transfer` (S3 upload) has no equivalent: download from `data.content` or the webhook body. `image_viewport`, `srt`, `svg`, `link_target` and the layout properties (`position_*`, per-layer `width`/`height`) are dropped; flag them to me.
- Rating layers import as a fixed image and barcode layers are not imported; if a `value` changes per render, tell me so I rebuild the layer in the Studio.
- Auth stays Bearer. Store the key as `ORSHOT_API_KEY`. Keys: https://orshot.com/docs/quick-start/get-api-key
- Official SDKs (Node, Python, Ruby, PHP) if you prefer them over fetch: https://orshot.com/docs/sdks
- Error codes: https://orshot.com/docs/error-reference

## 4. URL API links

Placid URL API links (`https://api.placid.app/u/{uuid}?title[text]=Hi&s=SIG`) become Orshot Dynamic URLs: https://orshot.com/docs/integrations/dynamic-urls
Shape: `https://api.orshot.com/v1/studio/dynamic-url/{name}.png?templateId=12345&title=Hi&sign=SIGNATURE`
- Plain `name=value` query parameters instead of `name[text]=value`. Only text parameters can be set through the URL. Image swaps must go through the render API.
- The signature comes from the template's Quick Connect → Dynamic URL panel; ask me for it. Do not port the HMAC signing code.
- Links already sent from api.placid.app keep working only while the Placid project exists. Only update new sends.

## 5. Automations

- n8n: replace the Placid node with the Orshot node (community package `n8n-nodes-orshot`). Docs: https://orshot.com/docs/integrations/n8n. I can also paste a ready workflow from the template's Quick Connect → Copy as → n8n workflow.
- Make: replace the Placid module with the Orshot module, or import the blueprint from Quick Connect → Copy as → Make blueprint. Docs: https://orshot.com/docs/integrations/make
- Zapier: replace the Placid action with Orshot → "Generate Image from Studio Template". Docs: https://orshot.com/docs/integrations/zapier
- Pipedream: https://orshot.com/docs/integrations/pipedream
- Anything that only speaks HTTP: Orshot's inbound template webhook accepts any JSON and maps keys to parameters: https://orshot.com/docs/integrations/webhooks
- If I use AI agents: Orshot for agents (MCP, skills): https://orshot.com/agents
  - MCP server URL: https://mcp.orshot.com/mcp (Claude, ChatGPT, Cursor, Codex and any MCP client). Docs: https://orshot.com/docs/integrations/mcp-server

## 6. Verify, then switch

- Keep Placid calls in place behind a flag until each Orshot render is compared with the Placid output on real data.
- Render each mapped template once with test data and show me the URLs.
- Then remove the Placid SDK, env vars and dead webhook handlers.

Full API index for anything not covered: https://orshot.com/llms.txt