Delete message

Deletes a message. Requires a secret key.

DELETE /v1/messaging/messages/{id}

Delete message

cURL

curl --request DELETE \
  --url https://api.tybritelabs.com/v1/messaging/messages/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'x-auth-token: <x-auth-token>'

200

{
  "success": true,
  "message_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "deleted_at": "2023-11-07T05:31:56Z"
}

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

Response

200

application/json

Message soft-deleted

success · boolean

Example:

true

message_id · string<uuid>

deleted_at · string<date-time>