Calculate a promotion's discount for a cart
Compute the discount a single promotion gives for a cart, server-side. The
result always matches the merchant’s own calculation, so your storefront never
reimplements the discount math (no subtotal × percentage on your side).
Send the cart you intend to charge — each line is the product, its quantity, and
the unit price you’re charging. How the discount is computed depends on the
promotion’s type:
discount(percentage) andfixed— a cart-wide discount applied to the eligible cart total.bundleandbogo— computed from the products present in the cart.
When the cart doesn’t qualify (the minimum purchase isn’t met, the promotion is
outside its active date/time window, or required products are absent), the
response is eligible: false with discount: 0 and a reason explaining why.
Marketplace storefronts: pass store_id (the merchant_store_id you
received with the promotion) to calculate against that merchant’s promotion.
Authorizations
API Key Authentication
Use your API key in the Authorization header:
Key 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.
Path Parameters
Query Parameters
The merchant whose promotion to calculate against. Required for marketplace
storefronts — pass the merchant_store_id you received with the promotion.
Ignored for single-store keys.
Body
Response
Success
The result of calculating a single promotion against a cart. The discount is computed server-side so it always matches the merchant's own calculation — you never reimplement the math.
The promotion that was evaluated.
How the promotion works. discount (percentage) and fixed are cart-wide
discounts; bundle and bogo are computed from the products in the cart.
discount, fixed, bundle, bogo Whether the cart qualifies for the promotion.
The discount amount to subtract from the cart total. 0 when the cart is
not eligible.
When eligible is false, a short explanation of why the cart does not
qualify (for example: minimum purchase not met, the promotion is outside its
active date/time window, or required products are absent). null when
eligible.

