taliiq
App
Taliiq

Constraints

Deletion rules and safe operation order for the public API

Download OpenAPI JSON

Live API testing

Paste a tq_live_… key from Settings → API Keys. Requests are sent through this docs server to /api/v1/… (no browser CORS). The key is kept in sessionStorage only.

Resource constraints

The API enforces the same safety rules as the dashboard. When a delete is blocked you receive HTTP 409 with code resource_in_use.

Agents

ActionRule
DeleteSet is_active to false first (stop the agent).
DeleteRemove linked web channels, SIP endpoints, phone numbers, and SIP trunks before deleting the agent.
CreateRequires system_prompt. Voice agents require voice_id.

Stop an agent before delete:

PATCH /api/v1/agents/{agent_id}
{ "is_active": false }

Channels (web widget)

ActionRule
DeleteSet is_active to false before deleting the channel.
Createagent_id must reference a published agent in your organization.

Tools

ActionRule
DeleteDetach the tool from all agents (PATCH agent with updated tools array) before deleting.

Files

ActionRule
DeleteClear knowledge_file on any agent using this file before deleting.
  1. Create agent — prompt, voice, pipeline fields
  2. Create web channel — link agent_id, configure allowed_domains
  3. Test — use the widget embed token from the channel response or dashboard

Use Try it live on each endpoint page after saving your API key. The playground calls /api/proxy/v1/… on this docs host, which forwards to your Taliiq backend at /api/v1/….