Skip to main content

Create a connector key

Open your Studio agent’s Settings → AI connectors → Connector keys. Enter a descriptive name, choose Read call history or Read history and place calls, and select an expiry of 30, 90, or 365 days. Copy the secret immediately: it is displayed only once. Keys belong to the selected Studio, not every agent you own. Studio owners and platform admins can manage them. Keep keys in your backend’s environment variables or secret manager. Never put one in browser code, a mobile app, a URL, or source control. At most 10 active keys are allowed per Studio, and at most 20 can be created per hour. Key creation requires an enabled Studio calling setup; listing and revocation remain available when calling is paused.

Authenticate an MCP client

Connect to https://www.lawtte.ai/api/mcp using the HTTP header:
What each permission reaches: get_onboarding_questions and list_voices need no credential at all. Keys can’t run set_up_calling or the receptionist draft and activation tools — those need a signed-in user, so use OAuth. All keys share the Studio’s billing and calling limits. Use check_call to validate a call without dialing. The same key works with the REST API (https://www.lawtte.ai/api/v1), with the same two permissions. Claude and ChatGPT sign in with OAuth instead and do not need a key.

Rotate or revoke

Create a replacement key, install it in your integration, verify it works, then revoke the old key. Revocation and expiry block subsequent requests. Lost secrets cannot be recovered. The key list displays a masked suffix, permissions, expiry, and last use. Existing legacy keys retain their previous permissions.

Configure a webhook

Open Settings → Webhooks, enter your receiver’s public HTTPS URL, select events, and save. Each Studio supports one endpoint, covering its Retell receptionist and outbound calls. IPv4 is required, only port 443 is supported, and URLs with credentials or a #fragment are rejected, as is any host that resolves to a private address. Redirects aren’t followed: a 3xx response counts as a failed attempt. LiveKit preview sessions do not currently emit these events. Choose any of call_started, call_ended, and call_analyzed. A call that fails before connecting may have no start event. Analysis can arrive after the end event. Copy the separate signing secret when it appears. Revoking a connector key does not change webhook signing. Saving an existing endpoint creates a new signing secret; update your receiver accordingly. Pending deliveries to the previous configuration are cancelled. Removing the endpoint also cancels pending deliveries. Use Send test event for a synthetic webhook.test payload. Refresh recent deliveries to see pending, delivered, failed, or cancelled status and response codes. A connection failure is shown separately from an HTTP response.

Payload and signature

Fields in call depend on the event. Provider credentials and internal call metadata are excluded. Treat transcripts and recordings as confidential data. Lawtte sends these headers:
  • X-Lawtte-Id: the stable event ID, also used in the payload.
  • X-Lawtte-Timestamp: Unix seconds for the current delivery attempt.
  • X-Lawtte-Signature: v1= followed by a hexadecimal HMAC-SHA256 digest of id.timestamp.rawBody, keyed by your whsec_... signing secret.
Verify against the exact raw request body before parsing JSON. Reject timestamps outside a five-minute window, compare signatures in constant time, and deduplicate by event ID. Retries use the same event ID and payload with a fresh timestamp/signature.
Return any 2xx response within 10 seconds and process the event asynchronously. Failures receive up to three retries, scheduled after 1, 5, and 30 minutes. Delivery runs every minute, so timings are approximate. Events may arrive out of order or more than once. History keeps the most recent 30 deliveries for seven days.