curl https://tawked.com/v1/email/messages/0199f1c2-7a41-7c3e-9d2b-5e8f1a2b3c4d/content \
-H "Authorization: Bearer tk_live_xxxxxxxxxxxxxxxxxxxx"const res = await fetch("https://tawked.com/v1/email/messages/0199f1c2-7a41-7c3e-9d2b-5e8f1a2b3c4d/content", {
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/email/messages/{id}/content",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "GET",
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.get(
"https://tawked.com/v1/email/messages/0199f1c2-7a41-7c3e-9d2b-5e8f1a2b3c4d/content",
headers={"Authorization": "Bearer tk_live_xxxxxxxxxxxxxxxxxxxx"},
)
data = res.json(){
"id": "0199f1c2-7a41-7c3e-9d2b-5e8f1a2b3c4d",
"subject": "طلبك 1042 في الطريق",
"html": "<p>مرحبًا سارة، طلبك 1042 في الطريق.</p>",
"text": "مرحبًا سارة، طلبك 1042 في الطريق.",
"kept_until": "2026-11-22T09:00:00+00:00"
}Get an email's content
Reads the copy the application kept of a message: its subject, HTML and text as sent (a template’s rendered output). Only while the application keeps previews (switched on in the console, under Email → Settings) and for the message’s 30 days. A live key with the explicit email:manage reads live messages; a test key with email:send reads its test messages; a sending key limited to one domain never reads it. Every read is recorded on the account’s trail, by the key.
curl https://tawked.com/v1/email/messages/0199f1c2-7a41-7c3e-9d2b-5e8f1a2b3c4d/content \
-H "Authorization: Bearer tk_live_xxxxxxxxxxxxxxxxxxxx"const res = await fetch("https://tawked.com/v1/email/messages/0199f1c2-7a41-7c3e-9d2b-5e8f1a2b3c4d/content", {
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/email/messages/{id}/content",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "GET",
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.get(
"https://tawked.com/v1/email/messages/0199f1c2-7a41-7c3e-9d2b-5e8f1a2b3c4d/content",
headers={"Authorization": "Bearer tk_live_xxxxxxxxxxxxxxxxxxxx"},
)
data = res.json(){
"id": "0199f1c2-7a41-7c3e-9d2b-5e8f1a2b3c4d",
"subject": "طلبك 1042 في الطريق",
"html": "<p>مرحبًا سارة، طلبك 1042 في الطريق.</p>",
"text": "مرحبًا سارة، طلبك 1042 في الطريق.",
"kept_until": "2026-11-22T09:00:00+00:00"
}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), email:manage (includes email:send), webhooks:manage, email:inbound, 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. email:manage and webhooks:manage are held only by a key someone chose them for: a full-access key, old or new, never holds them. email:inbound, which reads, deletes and forwards received e-mail, is opt-in on every key, full access included: a key holds it only when it was turned on when the key was created. 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.