GET/api/global-chatbot/demo/history

Loads the message history of a demo conversation so that it is preserved when the demo is reopened.

Pass `session_id` and `visitor_id` as query parameters; both must come from the same demo conversation. In the `data` object, the response contains the `messages` list with `id`, `role`, `text` and `created_at`. The call is read-only and idempotent. If either parameter is missing, the server responds with 400 `PARAMS_REQUIRED`. If the session is no longer known, start a new demo conversation.

Overview

Call: GET /api/global-chatbot/demo/history. This endpoint belongs to the “Demo Chatbot and SSO” group of the Zentor App API. It is publicly accessible and requires no authentication. The call is idempotent: repeating it with the same input returns the same result. Required parameters: session_id (query), visitor_id (query). Documented error cases: 400 PARAMS_REQUIRED. The example response below shows the structure of a successful JSON response.

Auth & Security

No authentication required

Idempotent: Yes

Parameters

session_id(query, string, required)— Session ID of the demo conversation
visitor_id(query, string, required)— Visitor ID (UUID) generated by the demo page

Example Response

{"ok":true,"data":{"messages":[{"id":"f248d929-c9ce-412d-aba8-43808ca1c9f7","role":"user","text":"Hello, what does Zentor cost?","created_at":"2026-07-20T17:07:02.240Z"},{"id":"3c26b6a6-4ca6-47a9-9669-a052082007ac","role":"assistant","text":"Ich kann dir zeigen, wie das für deinen Anwendungsfall aussehen würde — ohne Verpflichtung.","created_at":"2026-07-20T17:07:02.329Z"}]}}

Error Codes

400 PARAMS_REQUIRED — `session_id` or `visitor_id` is missing.

Verified behaviour

An existing demo session returns 200 with the history; missing parameters return 400 `PARAMS_REQUIRED`.

Demo Chatbot and SSO

POST /api/global-chatbot/demoSends a message to the public demo chatbot at zentor-app.de/demo and returns its reply. The demo can be tried out in the browser without registering.POST /api/global-chatbot/demo/pollFetches new messages of a demo conversation, for example when a Zentor team member has taken over the conversation. The demo page calls the endpoint at intervals.POST /api/global-chatbot/demo/ratingStores the rating of a demo conversation (helpful or not helpful) with an optional comment.POST /api/global-chatbot/demo/trackRecords anonymous usage events on the demo page for Zentor's visitor statistics.POST /api/global-chatbot/demo/voice-transcribeConverts a voice recording on the demo page into text (voice input), if the demo's voice feature is enabled.POST /api/global-chatbot/demo/voice-speakConverts text into speech (voice output on the demo page), if the demo's voice feature is enabled.GET /api/sso/:tenantSlug/statusChecks whether single sign-on (SAML or OIDC) is set up for an account. The sign-in page uses the result to offer SSO sign-in.GET /api/sso/:tenantSlug/oidc/startStarts sign-in via OpenID Connect and redirects the browser to the configured identity provider.GET /api/sso/:tenantSlug/oidc/callbackReceives the identity provider's redirect after OIDC sign-in and redirects the browser back to Zentor App.GET /api/sso/:tenantSlug/saml/startStarts sign-in via SAML and redirects the browser to the configured identity provider.POST /api/sso/:tenantSlug/saml/acsAssertion Consumer Service (ACS): receives the identity provider's signed SAML response via form POST.GET /api/sso/:tenantSlug/saml/metadataReturns the Zentor App SAML metadata (XML) for import into your identity provider.

Related articles

← Demo Chatbot and SSO