curl -X POST https://tawked.com/v1/chat/attendant/publish \
-H "Authorization: Bearer tk_live_xxxxxxxxxxxxxxxxxxxx"const res = await fetch("https://tawked.com/v1/chat/attendant/publish", {
method: "POST",
headers: {
Authorization: "Bearer tk_live_xxxxxxxxxxxxxxxxxxxx",
},
});
const data = await res.json();<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://tawked.com/v1/chat/attendant/publish",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_HTTPHEADER => [
"Authorization: Bearer <token>"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}import requests
res = requests.post(
"https://tawked.com/v1/chat/attendant/publish",
headers={"Authorization": "Bearer tk_live_xxxxxxxxxxxxxxxxxxxx"},
)
data = res.json(){
"version": 1,
"published_at": "2026-10-15T09:01:00Z"
}{
"error": "invalid_request"
}{
"error": "unauthorized"
}{
"error": "live_key_required"
}{
"error": "attendant_no_draft"
}{
"error": "attendant_not_ready",
"problems": [
{
"code": "title_long",
"choice_id": "c_prices",
"field": "title",
"max": 24
},
{
"code": "no_team_choice",
"choice_id": null,
"field": "choices",
"max": null
}
]
}{
"error": "too_many_requests"
}{
"error": "internal_error"
}Publish the auto-attendant
For a connected app’s key alone, with chat:attendant in its connection’s grant: an application’s own key, full access included, answers 403 insufficient_scope, and builds its auto-attendant in the console. Takes no body. The saved draft becomes the next version and the live menu: while the auto-attendant is on, customers get it from their next new conversation. A draft with problems is refused with 422 attendant_not_ready and its problems; before any draft was saved, 409 attendant_no_draft. Recorded in the client’s account record under the app’s name.
curl -X POST https://tawked.com/v1/chat/attendant/publish \
-H "Authorization: Bearer tk_live_xxxxxxxxxxxxxxxxxxxx"const res = await fetch("https://tawked.com/v1/chat/attendant/publish", {
method: "POST",
headers: {
Authorization: "Bearer tk_live_xxxxxxxxxxxxxxxxxxxx",
},
});
const data = await res.json();<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://tawked.com/v1/chat/attendant/publish",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_HTTPHEADER => [
"Authorization: Bearer <token>"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}import requests
res = requests.post(
"https://tawked.com/v1/chat/attendant/publish",
headers={"Authorization": "Bearer tk_live_xxxxxxxxxxxxxxxxxxxx"},
)
data = res.json(){
"version": 1,
"published_at": "2026-10-15T09:01:00Z"
}{
"error": "invalid_request"
}{
"error": "unauthorized"
}{
"error": "live_key_required"
}{
"error": "attendant_no_draft"
}{
"error": "attendant_not_ready",
"problems": [
{
"code": "title_long",
"choice_id": "c_prices",
"field": "title",
"max": 24
},
{
"code": "no_team_choice",
"choice_id": null,
"field": "choices",
"max": null
}
]
}{
"error": "too_many_requests"
}{
"error": "internal_error"
}Authorizations
Authorization: Bearer . An application key (tk_live_, tk_test_) has full access, which covers every product and any product added later, or custom access, chosen when the key is created: one or more of the scopes verify:check, verify:send (includes verify:check), notifications:read, notifications:send (includes notifications:read), email:read, email:send (includes email:read), notifications:templates (includes notifications:read), chat:menus, chat:attendant. No key made on the API keys page holds notifications:templates, full access included: the three template writes answer such a key 403 insufficient_scope. A connected app's key holds it. Nor chat:menus: the five conversation menu operations answer such a key 403 insufficient_scope, and a connected app's key holds it once the client approved it. Nor chat:attendant: the five auto-attendant operations answer such a key 403 insufficient_scope too, and a connected app's key holds it once the client approved it. A call outside the key's access answers 403 insufficient_scope and names the scope it needs in the WWW-Authenticate response header. A partner key (tk_partner_) always has full access. Whatever its access, a key is a server-side secret.
Headers
A 1 to 128 printable-ASCII-character key you generate, scoped to your API key. Replaying it with the same request answers the original 2xx unchanged, with the response header Idempotent-Replayed: true, and runs nothing again; the same key with another request answers 409 idempotency_key_reused, and a request still in flight 409 idempotency_in_progress. A refused request is never stored, so a corrected retry under the same key runs. Keys expire after 24 hours.