Refreshing demos
How refreshes keep demos current without changing embed code.
Refreshing demos
A refresh records the demo again. The embed URL stays the same, and the latest ready version is served automatically.
Use refreshes when the product UI changed, the copy changed, or a demo environment now has better data.
Refresh methods
| Method | Best for |
|---|---|
| Manual refresh | One-off fixes from the dashboard. |
| Scheduled refresh | Demos that should stay current without deploy hooks. |
| Webhook refresh | CI/CD pipelines that know exactly when a deploy finished. |
| API refresh | Product-owned workflows and internal tools. |
Refresh one demo
bashcurl -X POST https://littledemo.com/api/v1/demos/demo_abc123/refresh \ -H "Authorization: Bearer ld_live_xxx"
Refresh a project
bashcurl -X POST https://littledemo.com/api/v1/projects/proj_abc123/refresh \ -H "Authorization: Bearer ld_live_xxx"
Refresh after deploy
bashcurl -X POST https://littledemo.com/api/v1/webhooks/projects/proj_abc123/refresh \ -H "X-Webhook-Secret: whsec_xxx"
The webhook endpoint queues refresh jobs for ready demos in the project.