Service Level Agreement management
Service Level Agreement management
POST Acknowledge an SLA breach — Marks one organization-owned SLA breach as acknowledged and records the concrete session user or API-key identifier that performed the transition.POST Create an SLA policy — Creates an SLA policy for the current organization. Admin access is required.DELETE Delete an SLA policy — Deletes one SLA policy from the current organization. Admin access is required.GET Get SLA status for a specific conversation — Returns the SLA status for one conversation in the current organization. Visitor tokens can only inspect their own conversations.GET Get SLA status overview for active conversations — Returns an aggregate SLA overview for up to the 500 most recently active open conversations in the current organization.GET List recent SLA breaches — Returns recent SLA breaches for the current organization. Results can be filtered by operator, policy, and time range, and at most 100 breaches are returned.GET List SLA policies — Returns all SLA policies configured for the current organization.POST Resolve an SLA breach — Marks one organization-owned SLA breach as resolved, records the concrete session user or API-key identifier, and sets the resolution timestamp.PUT Update an SLA policy — Updates an existing SLA policy in the current organization. Admin access is required.Was this page helpful?
Export visitor data (GDPR data subject access request)
Exports all data associated with a visitor as a JSON attachment. Admin-only. Records a gdpr_requests entry. The export includes the visitor profile, conversations, visitor-authored messages, and CSAT responses for that visitor. Access requires an active organization administrator session or an organization API key with the `gdpr:write` scope. API-key calls also require the automation API module. Data is isolated to the authenticated organization; identifiers from another organization or site are not disclosed.
Acknowledge an SLA breach
Marks one organization-owned SLA breach as acknowledged and records the concrete session user or API-key identifier that performed the transition. Use this when the team has seen the breach but has not resolved it yet. Access requires an active organization administrator session or an organization API key with the `sla:write` scope. API-key calls also require the automation API module. Data is isolated to the authenticated organization; identifiers from another organization or site are not disclosed.