Danvas
Danvas
DashboardSupportWelcome

👤 USER DOCS

User Guides

Getting Started

Getting StartedDashboard & OnboardingApp Settings

Tutorials

Tutorial: Setting Up Shift Tasks & ClosersTutorial: Managing Incidents in the InboxTutorial: Tracking Compliance & Sync StatusTutorial: Operational Workflows with the AI AssistantTutorial: Building & Deploying Custom Checklists

Daily Operations (Staff)

Shift Workspace & TasksService Day SetupDaily Line-UpStaff Service Day ReportsForms

Communication & Chat

Messages & AnnouncementsUnified Operations InboxAI Assistant

Manager & Admin Guides

Daily Line-Up SetupStaff SchedulingManaging LocationsNPS and Guest FeedbackCouponsContacts and Guest HistoryManager CloseoutsDaily Line-Up & ComplianceAnalyticsIncident ReportingWhistleblower Concerns & FeedbackAdmin Tools

⚙️ DEVELOPER DOCS

Getting Started

Getting StartedDevelopmentDeployment Guide

Architecture

Architecture OverviewExplanation: AI Integration & Tenant SecurityExplanation: Dynamic Forms Engine DesignExplanation: Compliance Ledger DesignExplanation: Live Sync & Data FreshnessData FlowArchitecture Decision Records

Core Domain

Core DomainDatabase ReferenceLocations DomainAuth & RBACScheduling DomainReports DomainIncidents DomainUnified Operations InboxLive Sync Data FreshnessToast Sync PipelineNotifications DomainCoupons and Guest NPSAudit Log & Compliance ArchitectureDesign Audit FindingsAI Chat IntegrationAnalytics & Tips Integration

Frontend

Frontend ArchitectureFormsLoading SkeletonsComponentsPWA & Offline ShellScreenshots

API Reference

API Reference

Endpoints

POS Sales APIOptimization Data APISchedule Shifts APIEmployee Export APIReports APIIncidents APIAI Chat APIPush Notifications APIWebhooks APICron API

Contributing

ContributingCode Examples

Security

Security & Compliance

Release Notes

What's New

Incidents API

Endpoints for reporting and managing operational incidents

Overview

The Incidents API provides programmatic access to the incident reporting system. It supports creating new incidents, adding comments, changing statuses, and escalating high-priority issues.

Endpoints

Report Incident

POST /api/incidents

Request Body

  • locationId: string (UUID, required)
  • type: "Injury" | "Near Miss" | "Spill / Slip Hazard" | "Complaint" | "Maintenance" | "Stockout" (required)
  • severity: "low" | "medium" | "high" | "critical" (required)
  • notes: string (incident description, required, max 5000 characters)
  • mediaUrls: array of string (optional, Vercel Blob URLs)
  • contactMode: "none" | "existing" | "new" (optional)
  • contactId: string (optional, UUID of existing contact)
  • contactName: string (optional, name for new contact)
  • contactPhone: string (optional, phone number for new contact)
  • contactEmail: string (optional, email address for new contact)
  • contactNotes: string (optional, notes for new contact)

Add Comment

POST /api/incidents/:id/comments

Request Body

  • content: string

Update Status

PATCH /api/incidents/:id

Request Body

  • status: "reported" | "investigating" | "deferred" | "resolved"

Related

Incidents Domain Architecture

Incident Reporting User Guide

API Overview

Reports API

Endpoints for submitting and retrieving shift and manager reports

AI Chat API

Conversational data querying with streaming responses

On this page

OverviewEndpointsReport IncidentAdd CommentUpdate StatusRelated