Skip to main content
Use POST /api/v1/ppt/presentation/edit when the original presentation should be updated in place. The endpoint deep-merges the supplied content into the targeted slides, preserves every unlisted slide, exports the requested format, and returns the same presentation ID.
This operation changes the stored presentation. Use derive when the original must remain unchanged.

Before you start

  • Create or open a presentation and copy its ID.
  • Use the admin username and password configured for the Open Source instance.
  • Fetch GET /api/v1/ppt/presentation/{id} to inspect slide indices and current content objects.
  • Remember that slide indices are zero-based.
For example, assume the first slide of a customer-success deck currently contains:
The examples below update that exact title and subtitle for the approved Q3 review. Replace these keys with the fields returned by your own presentation.

Update selected fields

Each entry in slides identifies a slide by index. Its content object is merged into the existing content, so send only the fields that should change.
The response contains the existing presentation ID and fresh export paths:
Prepend PRESENTON_URL when a returned path is relative.

Python example

Edit safely

  • Read the presentation first instead of guessing content-field names.
  • Send the smallest possible patch; unrelated fields remain unchanged.
  • Verify chart and table structures before replacing nested values.
  • Export and review the result after every automated edit.
  • Avoid concurrent edits to the same presentation unless your application coordinates them.

Create a copy instead

Derive a new presentation and preserve the source deck.