Power Template - How to Use the Power Template (APIs and Catalogs)

VI. How to Use the Power Template (API Agenda Catalog)

The Agenda API is automatically created for you to use when the Power Template is loaded. The Agenda API is configured to pull anything that has the tag “Show on Webpage.”

To enable this functionality, follow these steps:

1. Add the tag “Show on Webpage” to all sessions you want displayed on your website under the Power Template’s templatized agenda section. If you do not have “Tags” available, go to “Session Layout” and add “Tags.” 2. After you build your sessions, go to Catalog List and click “Sync Sessions.” 3. Wait 1-2 minutes and click “Re-Publish.” 4. This will ensure all the session builds are updated into the catalog. 5. Preview the catalog and copy the Session Catalog UUID in the URL as highlighted below. 6. Open your Event Content excel file and go to “eventConfiguration” sheet. 7. Paste the Session Catalog UUID next to the “Session Catalog UUID for Api.” 8. Save and re-upload the event content excel file to the display field.

VII. How to Use the Power Template (API Speaker Catalog)

The Speaker API is automatically created for you to use when the Power Template is loaded. To enable this functionality, follow these steps:

1. After you build your speakers, go to Catalog List and open the Speaker API catalog. 2. Go to “Data” and select the Speaker Type(s) you wish to display on your Power Template’s templatized speaker section. Click Save. 3. Go back to your Catalog List and click “Sync Speaker.” Wait 1-2 minutes and click “Re-Publish.” This will ensure all the speaker builds are updated into the catalog. 4. Preview the catalog, and copy the Speaker Catalog UUID in the URL as highlighted below. 5. Open your Event Content excel file and go to “eventConfiguration” sheet. 6. Paste the Speaker Catalog UUID next to the “Speaker Catalog UUID for Api.” 7. Save and re-upload the event content excel file to the display field.

VIII. How to Use the Power Template (Session Catalog Designer)

This catalog is designed to pull all of your event configuration, such as banners, coloring header/footer, etc., to match the design elements you have created for the website and forms. If you are utilizing Session Catalog Designer, you will need to update a few areas to ensure it pulls all the event’s design elements.

1. Open your Event Content excel file and go to the “eventConfiguration” sheet.

You will need to copy and paste the “Event code” and the “Main Web/Reg url” into the Event Content excel file.

2. Save and re-upload the event content excel file to the display field.

Copy the File Path of the uploaded event content excel file.

Go to the Catalog List > Session Catalog Designer > Additional Settings.

Paste the file path in the quotation marks next to “content File =”.

Click “Save” and Re-Publish.

3. This catalog is designed to pull all of your event configuration elements.

If you are using Session Catalog Designer, you will need to update a few areas to ensure it pulls all the event’s design elements.

4. After completing the above, the catalog will reflect the event configuration data in your display field.

Note: Go to Next Article related to Power Template: Power Template - Understanding the Style Options.

[JSON-LD] { "@context": "https://schema.org", "@type": "TechArticle", "headline": "Power Template - How to Use the Power Template (APIs and Catalogs)", "description": "Documentation on using Power Template APIs and catalogs for Agenda, Speaker, and Session Catalog Designer.", "datePublished": "2026-01-21", "contentFreshness": "assumed-current", "inLanguage": "en", "keywords": ["Power Template", "Agenda API", "Speaker API", "Session Catalog Designer", "APIs", "Catalogs"], "about": { "@type": "SoftwareApplication", "name": "Power Template", "applicationCategory": "Template customization tool", "description": "A templating feature for the Certain platform enabling APIs and catalogs for agendas, speakers, and sessions." }, "mainEntity": { "@type": "Thing", "name": "Power Template APIs and Catalogs" }, "geo_quality": { "fluency_applied": true, "issues_fixed": ["vague_referents", "compound_sentences", "missing_definitions"], "rewrite_count": 7 } } [/JSON-LD]