Skip to main content
NavTalk supports pushing real-time conversation events and complete session records to your server via Webhook, enabling you to:
  • Receive real-time session lifecycle events (session creation, message output, session closure)
  • Receive complete session records when a session ends
  • Persist conversation data to databases
  • Implement business logic processing and data analysis

How It Works

Webhook uses HTTP POST requests to push events to your configured server endpoint. NavTalk triggers Webhooks in the following scenarios:
  1. Real-time Event Push (/api/webhook/message): Immediately pushes when specific events occur in a session
  2. Session Record Push (/api/webhook/session): Pushes complete session data when a session ends

Event Types

Real-time Events (Message Webhook): Pushed through the /api/webhook/message endpoint, including the following event types: Session Records (Session Webhook): Pushed through the /api/webhook/session endpoint, including complete message list (all conversation content), session start time, session end time, and session ID.

Quick Start

Select your programming language and framework to create a Webhook endpoint. Below are example code snippets for Webhook controller/route handling:
Data model definitions:
Dependency configuration files:
Configure your Webhook URL in the NavTalk console: Log in to the NavTalk Console, go to project settings, and configure the following Webhook URLs:
  • Real-time Event Webhook: https://your-domain.com/api/webhook/message
  • Session Record Webhook: https://your-domain.com/api/webhook/session
Deploy your application (Spring Boot / Flask / ASP.NET Core), ensure your server is publicly accessible, create a test session in NavTalk, and check your server logs to confirm Webhook events have been received.

Data Format

MessageData Format - Real-time event data format:
Field Descriptions: SessionData Format - Complete session record data format: