Edit landing page via API post-generation
A
Abe Dearmer
Hi Andy, thanks for the request. To make sure we scope this correctly, can you share a bit more about what “edit the landing page” means in your workflow after it’s generated?
A few specifics that would help:
1) Which landing page fields do you need to update via API (for example: display name, headline, body copy, CTA text, CTA URL, thumbnail, branding, custom variables)?
2) Are you looking to update a single landing page tied to one video, or a template that affects many pages?
3) What identifier would you want to use to target the page for updates (video ID, landing page ID, external ID from your system)?
4) For the phonetic name use case, is the goal to initially generate with a “safe” phonetic value, then later replace it with the real name once verified? If so, what triggers the change and how quickly does it need to happen?
5) Do you need partial updates (patch specific fields) or full replacement (send the entire landing page payload each time)?
6) Any permissions or safety requirements (for example: restrict edits after a page has been viewed, or keep an audit trail of changes)?
If you can provide an example of the current API call you use to generate the landing page and a sample of what you’d want to change afterward (even a mock JSON payload), we can confirm the best approach and what endpoints would be needed.