Skip to main content
What you will learn: This page covers every feature of Livia: chat conversations, automated routines, action approvals, business opportunities, privacy controls, usage tracking, and integration diagnostics.

🔢 Table of Contents

  1. Overview
  2. Prerequisites
  3. Endpoint Reference
  4. Chat
  5. Conversations
  6. Routines
  7. Approvals
  8. Opportunities
  9. State & Capabilities
  10. Privacy & Retention
  11. Audit Log
  12. Settings & Usage
  13. Integration Diagnostics
  14. Error Handling
  15. Best Practices

1. Overview

What is Livia - 360 Assistant?

Livia - 360 Assistant is a plan-gated AI assistant built directly into ZappWay. Unlike the AI Employees (which handle external customer conversations), Livia works for you and your team internally. Key Capabilities:
  • 💬 Natural language chat with full conversation history
  • 🔄 Automated routines — recurring tasks that run on schedule
  • Action approvals — review AI-proposed actions before they execute
  • 📈 Business opportunities — AI-surfaced insights from your data
  • 🔒 Privacy controls — full data retention management
  • 📋 Audit log — complete history of every action the assistant took

Plan Requirement

Livia is available only on plans that include the personal_assistant feature flag. Attempting to access any endpoint without the required plan returns:

2. Prerequisites

  • Active ZappWay account with a plan that includes Livia
  • Authenticated session (Livia is always user-bound, not organization-bound at the chat level)
  • At least one integration configured for full functionality (optional for basic chat)

3. Endpoint Reference


4. Chat

Send a Message

The chat endpoint is the core of Livia. It accepts a message and returns either a streaming Server-Sent Events (SSE) response or a standard JSON response.
Request Body: Example (non-streaming):
Livia keeps the interaction language stable across the conversation. Short ambiguous replies such as “ok” do not replace that choice. Interface labels continue to use the account’s interface locale. Route and integration guidance is generated from verified product teachings. If a route, action, or integration capability cannot be verified, Livia reports that limitation rather than inventing a label, link, or executable action. Example (streaming):

Streaming Response Format (SSE)

When stream: true, the endpoint returns Content-Type: text/event-stream. Events: Heartbeat: A : heartbeat comment is sent every 15 seconds to keep the connection alive. Timeout: Streams are automatically closed after 90 seconds. TypeScript (streaming):
Rate Limiting: The chat endpoint enforces plan-based rate limits. Rate limit headers are included in every response:
  • X-RateLimit-Limit
  • X-RateLimit-Remaining
  • X-RateLimit-Reset

5. Conversations

Livia maintains persistent conversation history. Each conversation is a thread of messages.

List Conversations

Returns all conversations for the authenticated user, ordered by last activity.

Create a Conversation

Get Messages in a Conversation

Cancel a Streaming Message

If a streaming response is in progress and you want to stop it:

Retry a Failed Message


6. Routines

Routines are automated tasks that run on a schedule. Livia can execute routines automatically or on demand.

List Routines

Response:

Create/Update a Routine

Toggle a Routine

Enable or disable a routine without deleting it:

Get Execution History

Returns the last N executions of a routine, including status (success/failed) and output.

Run a Routine Manually

Request Body:

7. Approvals

Some actions proposed by Livia require your explicit approval before execution. The approvals system gives you full control over automated actions.

List Pending Approvals

Response:

Approve an Action

The action executes immediately upon approval.

Reject an Action

The action is discarded. You can optionally provide a reason.

8. Opportunities

Livia surfaces business opportunities — AI-identified insights from your conversation data, contacts, and integrations.

List Opportunities

Update an Opportunity

Mark an opportunity as actioned, dismissed, or in-progress:
Request Body:

9. State & Capabilities

Get Assistant State

Returns the current state of Livia, including context, integrations status, and active features.

Get Capabilities

Returns the list of actions and features available to the assistant based on your plan and configured integrations.
Response:

10. Privacy & Retention

You have full control over the data Livia stores.

Get Privacy Settings

Delete All Personal Data

Permanently deletes all conversation history, routine data, and personal context stored by the assistant.
⚠️ This action is irreversible. All conversation history and personal data will be permanently deleted.

Get Retention Policy

Update Retention Policy

Request Body:

11. Audit Log

Every action Livia takes is logged for accountability and review.

Get Audit Log

Supports pagination and date filtering via query parameters.

Export Audit Log

Download the full audit log as a file:
The response is a downloadable file (CSV or JSON format, based on implementation).

12. Settings & Usage

Update Settings

Configure Livia behavior:

Get Usage

View your Livia usage statistics (message count, routine executions, etc.):
Response:

13. Integration Diagnostics

Run diagnostics on a specific integration to verify connectivity and permissions:
Path Parameters:

14. Error Handling

Status Codes


15. Best Practices

Streaming Chat

  • Always implement client-side disconnect handling to call the cancel endpoint if the user navigates away
  • Show a loading indicator while waiting for the first chunk event
  • Display text progressively as chunk events arrive for a better UX

Routines

  • Start with simple routines (e.g., daily summaries) before complex multi-step automations
  • Use the execution history to verify routines are running correctly before enabling new ones
  • Set up routines to run during off-peak hours (early morning) to avoid competing with interactive usage

Approvals

  • Check pending approvals regularly — time-sensitive actions may expire
  • Review the action payload carefully before approving, especially for actions that send external communications
  • Use the reject endpoint to provide feedback that helps the assistant learn your preferences

Privacy

  • Set a retention policy that matches your organization’s data governance requirements
  • Export the audit log periodically for compliance records
  • Use DELETE /privacy as part of offboarding workflows for departing team members