E-commerce API
The MOOD MNKY E-commerce API provides a comprehensive set of endpoints for interacting with our e-commerce system. These APIs enable seamless integration with our shopping experience, custom product creation, and personalized customer management.Overview
The E-commerce API is organized into several logical sections, each focusing on a specific aspect of the e-commerce experience:Products API
Manage and retrieve product information, including details, variants, inventory, and media assets.
Orders API
Create, manage, and track orders, including order processing, fulfillment, and history.
Cart API
Manage shopping carts, add/remove items, apply discounts, and prepare for checkout.
Customers API
Manage customer accounts, profiles, addresses, and preferences for a personalized experience.
Custom Blends API
Create and manage personalized fragrance blends, scent profiles, and custom product formulations.
Key Features
Seamless Storefront Integration
The E-commerce API provides all the functionality needed to build a complete custom shopping experience, while leveraging our robust backend systems for inventory management, payment processing, and order fulfillment.Custom Product Creation
Our API includes specialized endpoints for creating and managing custom fragrance blends, allowing customers to design personalized products that meet their unique preferences and needs.Customer Profile Management
Comprehensive customer management capabilities allow for storing detailed customer profiles, preferences, and order history to enable highly personalized shopping experiences.Order Processing and Fulfillment
End-to-end order management from creation through fulfillment, with detailed status tracking and notifications at each step.Common Patterns
All E-commerce APIs follow consistent patterns and conventions:Authentication
All E-commerce API endpoints require authentication using either:- Customer Authentication: For customer-facing applications using JWT tokens
- Admin Authentication: For administrative access using API keys with appropriate permissions
Response Format
Responses follow a consistent JSON format:Error Handling
Errors follow a consistent format with appropriate HTTP status codes:Pagination
List endpoints support standard pagination parameters:| Parameter | Description | Default |
|---|---|---|
| page | Page number (1-based) | 1 |
| limit | Items per page | Varies by endpoint |
Getting Started
To get started with the E-commerce API:- Create an API key in your developer dashboard
- Review the authentication documentation
- Explore the specific API sections for detailed endpoint information
Rate Limits
The E-commerce API implements rate limiting to ensure system stability:| Authentication Type | Rate Limit |
|---|---|
| Anonymous | 60 requests per hour |
| Customer | 1000 requests per hour |
| Admin | 5000 requests per hour |
Best Practices
- Use appropriate scopes for API keys to limit access to only the required functionality
- Implement webhook listeners for real-time updates instead of polling
- Cache product information when appropriate
- Use the bulk endpoints for batch operations when available
- Implement proper error handling for a smooth user experience