Skip to main content
GET
cURL
Guide: Sending email

Authorizations

Authorization
string
header
required

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). 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. 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.

Path Parameters

id
string<uuid>
required

Response

Delivered / Bounced

id
string
status
string
from
object
to
string
subject
string
reference
string
price_halalas
integer
created_at
string<date-time>
error
object | null
sent_at
string<date-time>
delivered_at
string<date-time> | null
bounced_at
string<date-time> | null
complained_at
string | null
failed_at
string | null
Last modified on October 13, 2026