Developers
API keys, webhooks and connecting an AI assistant over MCP.
- API keys: reading your workspace from your own systemsCreate a key, choose what it may do, restrict where it can be used from, and revoke itDevelopers
- API overview and authenticationThe ClientTurn REST API at a glance, how keys and permissions work, rate limits, errors and every endpoint available todayDevelopers
- Creating leads with the APIThe full reference for POST /api/v1/leads, including the Idempotency-Key header, the request body and every outcome it can returnDevelopers
- Reading and updating leads with the APIReference for GET /api/v1/me, GET and PATCH /api/v1/leads, and GET /api/v1/events, with parameters and response shapesDevelopers
- Webhooks: being told the moment something happensThe event catalogue, the payload envelope, how to verify the signature, and how retries and failures workDevelopers
- Setting up a webhookStep by step, add an HTTPS endpoint, choose its events, store the signing secret, send a test and read the delivery logDevelopers
- Connecting an AI assistant (MCP)Let Claude, Codex, Gemini or another MCP client work inside your workspace safely, with the permissions you chooseDevelopers
- MCP tools and approvalsWhich tools an AI assistant gets over MCP, which ones run straight away, which wait for a person, and how to approve or refuse themDevelopers