Skip to main content
GET
/
v1
/
messaging
/
threads
/
{id}
/
messages
Get messages in a thread
curl --request GET \
  --url https://api.tybritelabs.com/v1/messaging/threads/{id}/messages \
  --header 'Authorization: Bearer <token>' \
  --header 'x-auth-token: <x-auth-token>'
{
  "messages": [
    {
      "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "message_content": "<string>",
      "sender_id": "<string>",
      "sender_name": "<string>",
      "attachments": [
        "<string>"
      ],
      "metadata": {},
      "read_at": "2023-11-07T05:31:56Z",
      "is_edited": true,
      "is_deleted": true,
      "edited_at": "2023-11-07T05:31:56Z",
      "deleted_at": "2023-11-07T05:31:56Z",
      "created_at": "2023-11-07T05:31:56Z",
      "updated_at": "2023-11-07T05:31:56Z"
    }
  ],
  "pagination": {
    "limit": 123,
    "next_cursor": "<string>",
    "has_more": true
  }
}

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

​
limit
integer
default:50
Required range: 1 <= x <= 200
​
cursor
string

Cursor for pagination (base64-encoded created_at value)

​
order
enum<string>
default:asc

Sort order — asc (oldest first, default) or desc (newest first)

Available options:
asc,
desc
​
fields
string

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

Allowed Fields:

  • id, message_content, message_type, sender_type, sender_id
  • sender_name, attachments, metadata, message_status, read_at
  • is_edited, is_deleted
  • created_at, updated_at

Response

Success

​
messages
object[]
​
pagination
object