Transform your Botble CMS eCommerce platform into a powerful, secure, and production-ready REST API.
Botble CMS REST API Connector is a complete API solution that exposes your eCommerce platform through a structured, versioned, and secure REST API. It allows external systems, websites, dashboards, third-party applications, integrations, and custom frontends to communicate seamlessly with your Botble CMS installation.
The connector is designed around Laravel best practices, providing optimized endpoints for products, categories, customers, authentication, orders, wishlists, checkout, wallet balances, and other core eCommerce operations.
Expose your Botble CMS eCommerce functionality through clean, consistent, and well-structured REST API endpoints.
Authentication is powered by Laravel Sanctum, providing secure API token management and protected access to customer-specific resources.
API endpoints are optimized using:
Laravel best practices
Database indexing
Eager loading
Pagination
Query optimization
Response optimization
Efficient relationship loading
All endpoints are organized under a versioned API structure:
/api/v1
This allows future API versions to be introduced without breaking existing integrations.
The API can be consumed by:
Web applications
Desktop applications
Mobile applications
POS systems
ERP systems
CRM platforms
Third-party services
Custom dashboards
Business intelligence systems
External eCommerce interfaces
Other backend services
The API is designed to work with the existing Botble CMS eCommerce infrastructure while providing a clean integration layer between Botble and external systems.
Complete customer authentication functionality including:
Customer registration
Email/password login
Logout
Token authentication
Social authentication
Current-user information
Account deletion
Access and manage product information through structured API endpoints.
Features include:
Product listing
Product details
Product search
Search suggestions
Product filtering
Product pagination
Product categories
Product pricing
Product images
Product attributes
Product variations
Product availability
Retrieve the complete product category structure.
Features include:
Parent categories
Child categories
Nested categories
Category details
Category-based product filtering
Authenticated customers can manage their wishlist through the API.
Features include:
Retrieve wishlist
Add product to wishlist
Remove product from wishlist
Toggle wishlist status
Provide API access to the complete purchasing workflow.
Features include:
Cart management
Add products to cart
Update cart quantities
Remove cart items
Calculate totals
Apply applicable pricing rules
Checkout
Order creation
Authenticated customers can retrieve their order information.
Features include:
Order history
Order details
Order status
Payment status
Fulfillment status
Order items
Order totals
Authenticated users can manage their customer information.
Features include:
Profile information
Customer details
Account settings
Authentication status
Account deletion
Provide access to customer wallet/store-credit information.
Features include:
Current wallet balance
Wallet transactions
Store credit information
All endpoints are available under:
/api/v1
These endpoints do not require authentication.
GET /api/v1/init
Returns API configuration, system information, supported features, and relevant platform settings.
GET /api/v1/products
Retrieve a paginated list of products.
Example:
GET /api/v1/products?page=1&per_page=20
Supported parameters may include:
page per_page search category brand sort order min_price max_price
GET /api/v1/products/{slug}
Retrieve detailed information about a specific product.
Example:
GET /api/v1/products/iphone-15-pro
GET /api/v1/products/search-suggest
Retrieve search suggestions based on a search keyword.
Example:
GET /api/v1/products/search-suggest?q=iphone
GET /api/v1/categories
Retrieve the product category hierarchy.
POST /api/v1/login
Authenticate a customer.
Request:
{ "email": "customer@example.com", "password": "password" }
Response:
{ "success": true, "message": "Login successful", "data": { "token": "TOKEN", "token_type": "Bearer", "user": { "id": 1, "name": "John Doe", "email": "customer@example.com" } } }
POST /api/v1/register
Create a new customer account.
Request:
{ "name": "John Doe", "email": "customer@example.com", "password": "password", "password_confirmation": "password" }
POST /api/v1/social-login
Authenticate or register a customer through a supported social authentication provider.
Authenticated endpoints require:
Authorization: Bearer {TOKEN}
GET /api/v1/me
Retrieve the currently authenticated customer's profile.
POST /api/v1/logout
Revoke the current authentication token.
DELETE /api/v1/account/delete
Permanently delete the authenticated customer account.
This endpoint supports privacy and account-management requirements.
GET /api/v1/wishlist
Retrieve the authenticated customer's wishlist.
POST /api/v1/wishlist/toggle
Request:
{ "product_id": 123 }
GET /api/v1/cart
Retrieve the current customer's cart.
POST /api/v1/cart/add
Request:
{ "product_id": 123, "quantity": 2 }
PUT /api/v1/cart/update
Request:
{ "product_id": 123, "quantity": 3 }
DELETE /api/v1/cart/remove
Request:
{ "product_id": 123 }
POST /api/v1/checkout
Create an order using the customer's current cart and checkout information.
GET /api/v1/orders
Retrieve the authenticated customer's orders.
Supports pagination:
GET /api/v1/orders?page=1&per_page=20
GET /api/v1/orders/{id}
Retrieve detailed information about a specific order.
GET /api/v1/wallet/balance
Retrieve the authenticated customer's wallet/store-credit balance.
Example response:
{ "success": true, "data": { "balance": 25000, "currency": "NGN" } }
All API responses should follow a consistent structure.
{ "success": true, "message": "Request successful", "data": {} }
{ "success": false, "message": "Validation failed", "errors": { "email": [ "The email field is required." ] } }
The API implements multiple security mechanisms including:
Laravel Sanctum authentication
Bearer token authentication
Request validation
Authorization checks
Rate limiting
CSRF protection where applicable
Input sanitization
SQL injection protection through Laravel's database layer
Secure password hashing
Protected customer resources
Permission-based access control
Sensitive endpoints require authentication and appropriate authorization.
API configuration can be managed through the Botble CMS administration environment.
Configuration options may include:
API enable/disable
API version
Authentication settings
Token configuration
Rate limits
Pagination limits
Allowed origins
API access controls
Response settings
Cache settings
Upload the API connector package to:
platform/plugins/
Example:
platform/plugins/rest-api/
From the Botble CMS administration panel:
Admin Panel → Plugins → REST API Connector → Activate
Navigate to:
Admin Panel → Settings → REST API
Configure the required API settings.
The API can be documented using an industry-standard specification such as OpenAPI 3.0.
Example:
/api/v1/docs
The documentation can provide:
Endpoint descriptions
Authentication requirements
Request parameters
Request bodies
Response structures
Error responses
HTTP status codes
Example requests
Example responses
The connector follows a structured Laravel architecture:
Client │ ▼ REST API │ ▼ Routes │ ▼ Controllers │ ▼ Requests / Validation │ ▼ Services │ ▼ Repositories / Models │ ▼ Botble CMS Database
This architecture keeps the API layer separated from the presentation layer while allowing it to leverage the existing Botble CMS business logic.
The API acts as an integration layer between Botble CMS and external systems.
┌─────────────────────┐ │ Botble CMS │ │ eCommerce │ └──────────┬──────────┘ │ ▼ ┌─────────────────────┐ │ REST API Layer │ │ /api/v1 │ └──────────┬──────────┘ │ ┌────────────────────┼────────────────────┐ │ │ │ ▼ ▼ ▼ Web Platforms ERP / CRM Systems External Services │ │ │ ▼ ▼ ▼ Websites Dashboards Integrations
The REST API provides external systems with a standardized way to interact with the Botble CMS eCommerce platform.
It provides access to:
Authentication
Customers
Products
Categories
Brands
Wishlist
Cart
Checkout
Orders
Payments
Wallets
Customer profiles
Product search
Product filtering
System configuration
The API is designed to be frontend-independent, meaning the API does not depend on any particular user interface, framework, device, operating system, or client application.
Any compatible client capable of making HTTP requests can consume the API.
September 08,2026 at 07:48 AM
Worth every penny.
Amaya Hendrix
San Diego, California, United State.
September 08,2026 at 07:48 AM
The product is working perfectly so far.
Amaya Hendrix
San Diego, California, United State.
September 08,2026 at 07:48 AM
Very good quality and fast delivery.
Amaya Hendrix
San Diego, California, United State.
September 08,2026 at 07:48 AM
Worth every penny.
Amaya Hendrix
San Diego, California, United State.
September 08,2026 at 07:48 AM
Good product and reliable seller.
Amaya Hendrix
San Diego, California, United State.
September 08,2026 at 07:48 AM
The quality is better than I expected.
Amaya Hendrix
San Diego, California, United State.
September 08,2026 at 07:48 AM
Nice product and good value for money.
Amaya Hendrix
San Diego, California, United State.
September 08,2026 at 07:48 AM
Delivery was fast and the product was well packaged.
Amaya Hendrix
San Diego, California, United State.
September 08,2026 at 07:48 AM
I had a great shopping experience.
Amaya Hendrix
San Diego, California, United State.
September 08,2026 at 07:48 AM
Excellent product. Highly recommended.
Amaya Hendrix
San Diego, California, United State.