Overview
The v3 Content API supports bothproduct_id
and variation_id
parameters for maximum flexibility. This allows you to use whichever ID type is most convenient for your integration.
Product vs Variation Relationship
- Product: The main entity that represents a content item in your library
- Variation: A specific configuration of a product (pricing, currency, etc.)
- Relationship: Each product has exactly one variation in the current system
Parameter Options
For most endpoints, you can use either:product_id
- Often more intuitive and readily availablevariation_id
- Provides direct access to the variation data
API Endpoints Supporting Dual IDs
GET /v3/content
PUT /v3/content
DELETE /v3/content
Bulk Operations
Migration Guide
From variation_id to product_id
If you’re currently usingvariation_id
parameters, you can:
- Keep using variation_id - No changes needed, full backward compatibility
- Switch to product_id - Often simpler for integrations
- Use both - Mix and match based on what’s available