Bagisto Shop REST API
68
AI ReadinessAI-Aware (B+)68/100
Official vendor OpenAPI document · agent-readyE 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbagisto.com%2Fbagisto" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbagisto.com%2Fbagisto" | 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 your Jentic One instance, 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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
B
Bagisto Shop REST API
- AI-Aware (B+)68/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
29%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
58%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Bagisto by hand means pointing at your self-hosted instance's configurable host, running the /customers/login call, and refreshing the returned JWT bearer token across the cart, checkout, and order endpoints. Through Jentic you install once, import the Bagisto Shop REST API from the API Directory, store the host and customer token once, and your agent calls it.
Permission scoping
Bagisto carries the product, cart-item, and coupon details in the request body or query rather than the URL path, and the JWT already scopes calls to the authenticated customer, so scoping is by operation: limit the agent to the operations it needs, such as GET /products/search and POST /cart/items. You choose those operations, so destructive ones like DELETE on /product-reviews are not included unless you add them.
Credential isolation
Your Bagisto customer JWT and host configuration are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search a storefront for products' or 'add an item to the cart', and Jentic returns the matching Bagisto operation with its input schema so the agent picks the right endpoint without reading the OpenAPI spec.
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.
Can I limit what my agent is allowed to do with the Bagisto Shop REST API?
Yes. Because you run your own self-hosted Jentic One instance, your own rules decide which Bagisto operations and credentials the agent can use. Since the customer JWT already scopes calls to the authenticated shopper and Bagisto carries product, cart, and coupon details in the request body rather than the URL, you scope by operation: grant only what the agent needs, such as GET /products/search and POST /cart/items. Destructive operations like DELETE on /product-reviews are excluded unless you explicitly add them.
GET STARTED