Get a variant's specifications
Returns the latest published specification version for a single product variant.
Important — this endpoint is keyed by VARIANT id, not product id. Specifications are
stored per variant, so the {id} path segment must be a variant UUID (e.g. the
variant_id from a product detail, or an id from GET /v1/product-specifications).
Passing a product id (or a variant that has no published specifications) returns
404 not_found — “No specifications found for this product”. To browse all specifications
across the catalog, use GET /v1/product-specifications (which lists them with their
variant_id).
Read access — works with a publishable or secret key.
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
The variant UUID whose specifications to fetch (NOT a product id). A product id returns 404 — specifications are variant-keyed.

