Add to cart
Add item to cart with automatic stock checking. If the same variant already exists in the cart, the quantity is incremented.
Variant Selection:
variant_idis required to specify which variant to add (e.g., Black vs Blue color)- For simple products (no variants), use the default variant’s ID
- Stock validation is performed against the specific variant
Cart Association:
- Provide
X-Session-Idheader for anonymous carts (before customer login) - Provide
customer_idin request body for authenticated customer carts - If both provided,
customer_idtakes precedence - If neither provided, returns 400 error
Key Type Support:
- Publishable keys (
tybrite_pk_*) — fully supported (browser/storefront) - Secret keys (
tybrite_sk_*) — also supported (server-side)
Anonymous Cart Example:
POST /v1/cart/items
Authorization: Bearer tybrite_pk_live_YOUR_API_KEY
X-Session-Id: session-abc123-xyz789
Content-Type: application/json
{
"variant_id": "83b6a47e-4f5c-4090-b8d3-4b606b78f1b4",
"quantity": 2
}
Authenticated Cart Example:
POST /v1/cart/items
Authorization: Bearer tybrite_pk_live_YOUR_API_KEY
Content-Type: application/json
{
"variant_id": "83b6a47e-4f5c-4090-b8d3-4b606b78f1b4",
"quantity": 2,
"customer_id": "650e8400-e29b-41d4-a716-446655440000"
}
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
API Key Authentication
Use your API key in the Authorization header:
Authorization: Bearer tybrite_sk_live_YOUR_KEYKey Types:
Secret Keys (Server-Side Only):
- Format:
tybrite_sk_live_*(production) ortybrite_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) ortybrite_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
Customer session access_token from /v1/auth/login or /v1/auth/verify-otp. Required whenever customer_id is supplied so the gateway can prove the caller owns that customer record. Anonymous (session-only) carts may omit it.
Session ID for anonymous carts (UUID or random string stored in localStorage). Optional if customer_id is provided in the body.
Body
Specific product variant UUID (required for multi-variant products)
"83b6a47e-4f5c-4090-b8d3-4b606b78f1b4"
Quantity to add
x >= 12
Customer UUID for authenticated carts (optional if using X-Session-Id)
"650e8400-e29b-41d4-a716-446655440000"
Legacy/optional online product UUID. Ignored when variant_id is provided; included for backwards compatibility.
"770e8400-e29b-41d4-a716-446655440000"

