POST/api/global-chatbot/demo/voice-transcribe

Converts a voice recording on the demo page into text (voice input), if the demo's voice feature is enabled.

Send `visitor_id` (UUID) and the audio file in the `audio` field as `multipart/form-data`. The response contains the recognised text. The endpoint corresponds to `POST /api/public/widget/voice-transcribe` but is bound to the demo on zentor-app.de. Error cases: 400 `INVALID_VISITOR_ID` (missing or invalid UUID), 403 `ORIGIN_DENIED` (call not from zentor-app.de), 413 `AUDIO_TOO_LARGE` (file too large) and 415 `AUDIO_TYPE_UNSUPPORTED` (format not supported).

Overview

Call: POST /api/global-chatbot/demo/voice-transcribe. 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 not idempotent: every successful call triggers the action again. Required parameters: visitor_id (body), audio (body). Documented error cases: 400 INVALID_VISITOR_ID, 403 ORIGIN_DENIED, 413 AUDIO_TOO_LARGE, 415 AUDIO_TYPE_UNSUPPORTED. The example response below shows the structure of a successful JSON response.

Auth & Security

No authentication required

Only accepts calls from https://zentor-app.de and https://www.zentor-app.de; no embed token is required for the demo.

Idempotent: No

Parameters

visitor_id(body, string, required)— Visitor ID, must be a valid UUID
audio(body, file, required)— Audio file (`multipart/form-data`)

Example Response

{"ok":false,"error":{"code":"INVALID_VISITOR_ID","message":"visitor_id muss eine gültige UUID sein."}}

Error Codes

400 INVALID_VISITOR_ID — `visitor_id` is missing or not a valid UUID.
403 ORIGIN_DENIED — The call does not come from zentor-app.de.
413 AUDIO_TOO_LARGE — The audio file exceeds the permitted size.
415 AUDIO_TYPE_UNSUPPORTED — The audio format is not supported.

Verified behaviour

An invalid `visitor_id` returns 400 `INVALID_VISITOR_ID`, a call from another domain 403 `ORIGIN_DENIED`. The success case is only possible from zentor-app.de.

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.GET /api/global-chatbot/demo/historyLoads the message history of a demo conversation so that it is preserved when the demo is reopened.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-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