Bagisto Shop REST API
✓ Official Vendor SpecE CommerceStorefrontbearer38 EndpointsREST
For Agents
Browse products and categories, manage carts and customer accounts, place orders, and submit reviews on a Bagisto storefront via 38 REST endpoints.
Use for: Search for products matching a keyword on a Bagisto store, Get the list of categories in a Bagisto storefront, Add an item to the current customer cart, Apply a discount coupon to the cart
Not supported: Does not handle vendor admin tasks, payment gateway integration, or custom storefront theming — use for storefront catalog browsing, cart, customer accounts, and checkout only.
Bagisto is an open-source Laravel-based e-commerce platform. The Shop REST API exposes 38 endpoints for the customer-facing storefront: product and category browsing, search, customer authentication, cart and checkout flows, address management, customer orders, and product reviews. JWT bearer tokens issued from /customers/login authenticate customer-scoped routes, while catalog and locale routes are publicly readable. The API targets a self-hosted Bagisto instance, so the base URL includes a configurable host.
Install Jentic One Beta
Connect the Bagisto Shop REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bagisto Shop REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Bagisto Shop REST API.
Search products and browse categories on a Bagisto storefront
Authenticate customers with JWT and surface their saved addresses and order history
Build, mutate, and coupon a cart through dedicated /cart and /cart/items endpoints
Retrieve available shipping and payment methods and place an order via /checkout/place-order
Submit, update, and moderate product reviews with full CRUD on /product-reviews
Localise responses across channels and locales using the /channels and /locales endpoints
Use Cases
Patterns agents use Bagisto Shop REST API for, with concrete tasks.
★ Headless Storefront
Front-end teams build a Next.js or Vue storefront against a Bagisto backend by consuming the REST API directly. Catalog browsing uses /products, /categories, and /products/search; cart and checkout use /cart and /checkout/place-order. Bagisto handles inventory, pricing, and order persistence server-side, so the frontend stays a thin presentation layer that ships independently.
Search products with GET /products/search?query=hoodie, add the top result to the cart via POST /cart/items, then place the order with POST /checkout/place-order.
Customer Self-Service Portal
Build a customer account portal where shoppers update profile details, manage saved addresses, and review past orders without going through the default Bagisto theme. Endpoints under /customers/* cover registration, login, profile, addresses, and order history. JWT tokens scope every call to the authenticated customer.
Authenticate via POST /customers/login, then GET /customers/orders and surface the five most recent orders in a profile dashboard.
Reviews and Catalog Sync
Pipe product catalog and review data out of Bagisto into search, recommendation, or review-aggregation systems. /products and /product-reviews provide read-only feeds; the review endpoints also support create, update, and delete for moderation workflows. Use /channels and /locales to handle multi-channel, multi-language stores correctly.
Page through GET /products to export the catalog, then GET /product-reviews to attach review counts and average ratings per product.
AI Agent Integration via Jentic
An agent built on Jentic can act as a shopping assistant: search Bagisto for items matching a user's request, add the chosen item to a cart, apply a coupon, and complete checkout. Jentic stores the customer JWT in MAXsystem, so the agent never holds the raw token.
Search Jentic for 'add an item to a bagisto cart', load the schema for POST /cart/items, then execute it with the chosen product ID and quantity.
Key Endpoints
38 endpoints — bagisto is an open-source laravel-based e-commerce platform.
METHOD
PATH
DESCRIPTION
GET
/products
Get products list
GET
/products/search
Search products
POST
/cart/items
Add item to cart
POST
/cart/coupon
Apply coupon to cart
POST
/checkout/place-order
Place order at checkout
POST
/customers/login
Customer login
GET
/customers/orders
Get customer orders
POST
/product-reviews
Create a product review
GET
/products
Get products list
GET
/products/search
Search products
POST
/cart/items
Add item to cart
POST
/cart/coupon
Apply coupon to cart
POST
/checkout/place-order
Place order at checkout
POST
/customers/login
Customer login
GET
/customers/orders
Get customer orders
POST
/product-reviews
Create a product review
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Customer JWTs for Bagisto are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped operation handles; raw tokens never enter agent context or logs. The Bagisto host configuration is also held centrally so agents do not need to manage the base URL.
Intent-based discovery
Agents search Jentic with intents like 'add to cart' or 'place an order' and Jentic returns the matching Bagisto operation with its input schema, so the agent picks the right endpoint without reading the OpenAPI spec.
Time to first call
Direct Bagisto integration: 1-3 days to wire login, cart, checkout, and order endpoints with proper JWT refresh. Through Jentic: under an hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Bagisto Shop REST API through Jentic.
What authentication does the Bagisto Shop REST API use?
Customer-scoped routes use HTTP Bearer auth with a JWT obtained from POST /customers/login (the bearerAuth scheme). Catalog and locale endpoints are public. Through Jentic, the JWT is held in the encrypted vault and is injected at execution time so the agent never sees it.
Can I place an order through the Bagisto API?
Yes. Build the cart with POST /cart and POST /cart/items, optionally apply a coupon via POST /cart/coupon, fetch eligible methods from GET /checkout/shipping-methods and GET /checkout/payment-methods, then call POST /checkout/place-order with the chosen methods to create the order.
What are the rate limits for the Bagisto Shop REST API?
Bagisto is self-hosted, so rate limits depend on the operator's deployment (Laravel throttling middleware). The OpenAPI spec does not declare global limits. Check https://api-docs.bagisto.com/ and your deployment's nginx or Laravel rate-limit configuration.
How do I search for a product through Jentic?
Search Jentic for 'search bagisto products', load the schema for GET /products/search, then execute it with the query string. Jentic injects the host configuration and any required auth headers, so the agent can run the call without bookkeeping.
Can customers manage their own addresses through this API?
Yes. GET /customers/addresses lists the customer's saved addresses, POST creates a new one, PUT /customers/addresses/{id} updates an existing entry, and DELETE removes it. All four require an authenticated JWT.
Does Bagisto support multiple languages and stores in this API?
Yes. GET /locales returns supported locales and GET /channels returns the configured sales channels for the Bagisto instance. Use these to localise product titles and to scope catalog browsing per channel.
GET STARTED