Evnao documentation
Product setup, API access, and recovery paths.
Core concept
Every web, social, or email conversation is a tenant-scoped ticket with persisted messages, source, status, priority, assignment, and automation mode.
The assistant may answer from approved knowledge and enabled read actions.
An agent owns the conversation. AI generation stops on every channel.
Messages persist, but no automatic reply is generated.
The interaction is resolved and the visitor may submit one structured rating.
GET /api/v1/tickets lists up to 100 tickets with cursor pagination and optional status and source filters.
GET /api/v1/tickets/:ticketId returns one ticket and its latest 100 non-internal messages.
PATCH /api/v1/tickets/:ticketId changes status, priority, or automation mode and requires tickets:write plus an Idempotency-Key.
curl -X PATCH https://evnao.com/api/v1/tickets/TICKET_ID \
+ -H "Authorization: Bearer evnao_live_YOUR_KEY" \
+ -H "Idempotency-Key: ticket-update-123" \
+ -H "Content-Type: application/json" \
+ -d '{"status":"RESOLVED"}'