Get single product pricing with dynamic pricing and multi-currency support
Calculate dynamic price for a single product with geographic currency detection.
Response Structure:
- Simple products: Flat structure with all data at root level
- Multi-variant products: Hierarchical structure with product-level data + variants array
- Each variant gets its own pricing calculation and price breakdown
Multi-Currency Support:
- Automatically detects currency based on customer location
- Converts prices from store’s base currency to detected currency
- Falls back to store’s default currency if no location provided
- Works with all variants in multi-variant products
Dynamic Pricing:
- Customer segment/tier-based pricing
- Volume/quantity-based discounts
- Region-specific pricing rules (applied per variant)
- Time-based promotions
Field Filtering:
- Root-level filtering: Reduce top-level fields
- Nested variant filtering: Filter specific variant fields using dot notation
- Example:
fields=name,price_range,variants.sku,variants.display_price,variants.stock - Bandwidth reduction: Up to 55% with nested filtering
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.
Path Parameters
Product UUID or variant UUID
Query Parameters
Comma-separated list of fields to return (reduces bandwidth by up to 55%).
Root-level fields: product_id, name, brand, description, total_stock, price_range, has_variants, variant_count, base_currency, display_currency, currency_symbol, exchange_rate
Variant fields (use dot notation): variants.variant_id, variants.sku, variants.display_price, variants.stock, variants.variant_attributes, variants.price_breakdown, variants.price_breakdown.*
Example (35% reduction): fields=product_id,name,brand,total_stock,price_range,variants
Example (55% reduction): fields=name,price_range,variants.sku,variants.display_price,variants.stock
City or region name for geographic currency detection.
Works with variants: All variant prices converted to detected currency.
Examples:
place_name=New York→ USDplace_name=London, UK→ GBPplace_name=Nairobi, Kenya→ KES
Customer latitude for precise currency detection (use with longitude).
Works with variants: All variant prices converted based on detected region.
Customer longitude for precise currency detection (use with latitude)
DEPRECATED: Use place_name instead.
Location/country for location-based pricing
Manual region override for pricing rules
Customer UUID for personalized pricing.
When provided, the worker resolves the customer's RFM segment and tier server-side (from the customers + customer_stores tables) and feeds them into pricing rule evaluation. There is no need to pass segment/tier directly.
Quantity for volume-based pricing
x >= 1Response
Successfully retrieved product with dynamic pricing and currency conversion.
Response Structure:
- Simple products: Flat structure with pricing at root
- Multi-variant products: Hierarchical with variants array, each variant has own pricing
Response includes:
- Product details with converted prices
- Price breakdown showing discounts per variant
- Pricing context with currency and region info
- Aggregate price_range for multi-variant products
Primary image URL for list views
Array of product media objects
Only present for simple products
Only present for simple products
Only present for simple products
Price in store's base currency (only for simple products)
Price after discounts before conversion (only for simple products)
Final price in customer's currency (only for simple products)
Detailed price calculation (only for simple products)
Sum of stock across all variants (only for multi-variant)
Price range calculated from variant display_prices (only for multi-variant)
Whether product has multiple variants
Number of variants (only for multi-variant)
Array of variants with pricing (only for multi-variant)
Store's base currency code
"EUR"
Customer's currency code
"GBP"
Currency symbol for display
"£"
Exchange rate applied
0.870171
Global context used for pricing rule evaluation. customer_segment
and customer_tier are resolved server-side from customer_id
(they are not request parameters).

