Create a follow-up Digital Sales Room (DSR) from a meeting

Creates a draft Digital Sales Room (DSR) as a follow-up for a completed meeting. AI-generated post-meeting summary, action items, decisions, risks, and shared content, then assembles them into a new DSR article by binding those values into the required dsrTemplateId's placeholders and content slots. Once the underlying article and draft DSR are created, internal (Seismic-licensed) meeting participants and invitees are automatically granted editor access to the draft so they can review and publish it. The meeting must have status Ended and must have at least one piece of resolvable content (from the meeting itself or the template) before a DSR can be created.

Note: Preparing the DSR template

The referenced dsrTemplateId must point to a DSR template prepared in advance with the placeholder tokens this endpoint substitutes, placed wherever the corresponding meeting content should appear in the template's text. Any of these tokens the template omits are simply left unfilled — none are required.

PlaceholderReplaced with
[[Meeting::Name]]The meeting's name
[[Meeting::Summary]]AI-generated meeting summary
[[Meeting::ActionItems]]AI-generated action items
[[Meeting::Decisions]]AI-generated decisions
[[Meeting::KeyDiscussions]]AI-generated key discussion points
[[Meeting::Risks]]AI-generated risks
[[Meeting::StartDate]]The meeting's start date

To have the meeting's own attached content and call recording included, the template must also contain a microsite.documents widget titled exactly Content presented (and, for the call recording, one titled exactly Call recording). Content with no matching widget in the template is still attached to the DSR, but degrades to the Files tab instead of the templated widget.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required

The globally unique identifier (UUID v4) of the meeting engagement to generate a follow-up Digital Sales Room (DSR) from. The meeting must have already occurred (status "Ended") since the DSR content is built from AI-generated summary, action items, and shared content. Example value "335daa1b-a995-4b18-b5c5-161f2f291667".

Body Params

DSR template selection. dsrTemplateId is required — there is no default layout.

uuid
required

The unique identifier (UUID v4) of an existing DSR template whose layout and content placeholders are used to build the follow-up DSR. Required and must not be an empty GUID; omitting it or supplying an empty/unresolvable value fails the request.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json