Restyle and refresh

Restyle and refresh sound similar, but they solve different problems.

Use restyle for visual changes

Restyle keeps the action script and records again with new presentation settings.

Use it for:

• changing the background;
• changing the mockup frame;
• changing cursor or click effects;
• trying a different recording template when the original path is still right.

bash
curl -X POST https://littledemo.com/api/v1/demos/demo_abc123/restyle \  -H "Authorization: Bearer ld_live_xxx" \  -H "Content-Type: application/json" \  -d '{    "presentation": {      "background": "midnight",      "mockup": "macos-dark",      "recordingTemplate": { "id": "cinematic" }    }  }'

Use refresh for product changes

Refresh re-runs the demo against the current target page.

Use it when:

• the UI changed;
• the data changed;
• the old recording path fails;
• the demo is embedded somewhere public and should stay current.

Refresh works for generated demos. Uploaded local recordings cannot be refreshed or restyled; re-record locally and upload a new video instead.

bash
curl -X POST https://littledemo.com/api/v1/demos/demo_abc123/refresh \  -H "Authorization: Bearer ld_live_xxx"

Use a new demo for a new story

If the prompt itself needs to change, create a new demo. That keeps the old embed stable while you review the replacement.