Skip to main content
Use this workflow when your application already owns the slide content and needs Presenton to render it with a Standard template. Each slide selects a template layout and supplies a content object that satisfies that layout’s JSON schema.

Before you begin

Create a Cloud API key and pass it as a Bearer token on every request:

1. Get Standard templates

List the templates available to the authenticated Cloud account:
Save the selected template’s id. You will use it in the next three requests. Use the optional default query parameter to filter the list: true returns default templates and false returns custom templates. See List Standard templates.

2. Get the template and its schemas

Retrieve the selected template by ID:
The response includes one entry in schemas for each template layout. The schema’s title is the layout ID to send as slides[].layout. The entire slides[].content object must validate against the corresponding schema.
The response above illustrates the shape of schemas. Layout IDs, component names, fields, types, and constraints vary by template. Always use the live response for the selected template.
See Get a Standard template.

3. Get the template example

The example endpoint returns representative layout and content pairs that already conform to the selected template’s schemas:
Use the example to understand the expected nesting and content density. Do not assume the example fields apply to a different template or layout. See Get a template example.

4. Create the presentation from JSON

Build each slide with a layout from the selected template and content that validates against that layout’s schema. Then send the result to the synchronous from-JSON endpoint:
See Create from JSON synchronously. Before submitting the request, validate each content object against its live schema. This catches missing fields, incorrect value types, length violations, and invalid array sizes before the rendering request.