Skip to main content
GET
/
v1
/
messaging
/
threads
/
{id}
Get thread details
curl --request GET \
  --url https://api.tybritelabs.com/v1/messaging/threads/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'x-auth-token: <x-auth-token>'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "customer_id": "<string>",
  "customer_name": "<string>",
  "customer_email": "<string>",
  "customer_phone": "<string>",
  "store_name": "<string>",
  "store_avatar": "<string>",
  "order_id": "<string>",
  "product_id": "<string>",
  "subject": "<string>",
  "last_message_at": "2023-11-07T05:31:56Z",
  "unread_count_customer": 123,
  "unread_count_store": 123,
  "is_archived": true,
  "is_muted": true,
  "is_pinned": true,
  "created_at": "2023-11-07T05:31:56Z",
  "updated_at": "2023-11-07T05:31:56Z"
}

Documentation Index

Fetch the complete documentation index at: https://docs.tybritelabs.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

API Key Authentication

Use your API key in the Authorization header:

Authorization: Bearer tybrite_sk_live_YOUR_KEY

Key Types:

Secret Keys (Server-Side Only):

  • Format: tybrite_sk_live_* (production) or tybrite_sk_test_* (sandbox)
  • Full read/write access to all endpoints
  • ⚠️ NEVER expose in client-side code or public repositories
  • Required for: write operations, authentication, payment verification, AI recommendations

Publishable Keys (Client-Safe):

  • Format: tybrite_pk_live_* (production) or tybrite_pk_test_* (sandbox)
  • Read-only access (GET requests only, plus POST semantic search)
  • ✅ Safe for client-side JavaScript, mobile apps, and public code
  • Allowed for: browsing products, search, CMS content, pricing queries

Endpoint-Specific Requirements:

  • Authentication endpoints (/v1/auth/*): Secret key required
  • Payment verification (POST /v1/payments/verify): Secret key required
  • AI Recommendations (POST /v1/recommendations): Secret key required
  • Semantic Search (POST /v1/search): Both key types allowed (read-only operation)
  • All write operations: Secret key required
  • All read operations: Both key types allowed

Using a publishable key for restricted operations returns 403 Forbidden.

Headers

​
x-auth-token
string
required

Customer session access_token. Required to prove ownership of the thread/message being accessed.

Path Parameters

​
id
string<uuid>
required

Query Parameters

​
fields
string

Comma-separated list of fields to include in the response.

Allowed Fields:

  • id, customer_id, customer_name, customer_email, customer_phone
  • store_name, store_avatar, order_id, product_id
  • subject, thread_type, status, priority
  • last_message_at, last_message_by, unread_count_customer, unread_count_store
  • is_archived, is_muted, is_pinned
  • created_at, updated_at

Response

Success

​
id
string<uuid>
​
customer_id
string | null
​
customer_name
string
​
customer_email
string
​
customer_phone
string | null
​
store_name
string
​
store_avatar
string | null
​
order_id
string | null
​
product_id
string | null
​
subject
string
​
thread_type
enum<string>
Available options:
general,
order_inquiry,
product_inquiry,
support,
complaint,
delivery,
return,
refund,
technical
​
status
enum<string>
Available options:
active,
resolved,
closed,
escalated,
pending
​
priority
enum<string>
Available options:
low,
normal,
high,
urgent
​
last_message_at
string<date-time>
​
last_message_by
enum<string>
Available options:
customer,
store,
system
​
unread_count_customer
integer
​
unread_count_store
integer
​
is_archived
boolean
​
is_muted
boolean
​
is_pinned
boolean
​
created_at
string<date-time>
​
updated_at
string<date-time>