Compliance API
Enterprise organizations can connect their eDiscovery, data-loss-prevention and records systems to Syntic through the Compliance API. This page covers the set-up and the decisions an organization needs to make.
Set up
Decide what to retain
In Settings → Data retention, choose how long chat records and Syntic Code transcripts are kept. The Compliance API can only return what is retained.
Create a compliance key
Primary owner only: Settings → Admin keys → New → Scopes: compliance:read (add compliance:write only for the system that applies deletions and holds). Restrict the key by IP.
Connect your tool
Point your eDiscovery or DLP tool at https://app.syntic.ai/v1/compliance with the key and the syntic-beta: compliance-2026-12-01 header. Most tools poll activities every few minutes and fetch records on demand.
Test with a legal hold
Create a hold on a test member, delete one of their chats from the app, and confirm the record is still returned.
Activity types
The full list is on the Compliance API overview.
Telling members
Members’ chats in Syntic’s apps under the organization’s plan are visible to the compliance key. Your acceptable-use policy should say so. Syntic shows members a notice in the apps when compliance access is enabled for their organization.
Responsibilities
| Syntic | Your organization |
|---|---|
| Keeps records for the retention you set, and longer under hold | Chooses retention periods and holds |
| Logs every compliance-key call in the audit feed | Protects the compliance key |
| Deletes records when asked through the API | Decides when deletion is lawful |