CS-Cart API

Name: CS-Cart API API
Brand: CS-Cart API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontbasic57 EndpointsREST

For Agents

Run a CS-Cart 2.0 storefront end-to-end: catalogue management, cart and checkout, order fulfilment, shipments, payments, and CMS pages.

Quickstart

Get started with CS-Cart API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"update an order status in CS-Cart"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with CS-Cart API API.

Manage the product catalogue with create, update, and delete on /products and /products/{product_id}

Manipulate the category tree and assign products to one or more categories

Inspect orders, line items, totals, and update fulfilment status through /orders/{order_id}

Create or update customer and admin user records and look them up by ID

GET STARTED

Start building with CS-Cart API API

Explore with Jentic

View OpenAPI Document

Use for: I need to add a new product variant with stock 100 and price 24.99, Update the order fulfilment status to 'shipped' once the warehouse dispatches, Get the cart contents for an abandoned shopping session, List all shipments associated with a specific order

Not supported: Does not handle payment processing, shipping rate quoting, or hosting infrastructure — use for CS-Cart catalogue, order, fulfilment, and CMS management only.

Jentic publishes the only available OpenAPI document for CS-Cart API, keeping it validated and agent-ready.

The CS-Cart API at version 2.0 is the broader REST surface for CS-Cart single-vendor stores and multi-vendor marketplaces. It exposes 57 endpoints covering products, categories, orders, users, carts, shipments, payments, and pages, giving access to the full storefront lifecycle from catalogue management through checkout and fulfilment. Authentication uses HTTP Basic auth with the store admin email and API key, and the base URL is templated against the store's own domain.

Use Cases

Patterns agents use CS-Cart API API for, with concrete tasks.

★ Headless Storefront Backend

Power a custom React or Vue storefront on top of CS-Cart by reading products and categories from the API and posting cart and order updates back. The 57-endpoint surface covers everything the front end needs, from product detail to checkout. This decouples merchandising from rendering and lets a single CS-Cart backend power web, mobile, and kiosk experiences.

Call GET /products with category filter for the front end, then POST cart updates through the cart endpoints and finalise via the order endpoints.

Marketplace Vendor Onboarding

Onboard a new vendor into a CS-Cart multi-vendor marketplace by scripting the user creation, store configuration, and starter catalogue load. The agent calls the user creation endpoint, then walks the products endpoints to import the vendor's initial catalogue. This shrinks vendor onboarding from days of manual work to minutes per vendor.

POST /users to create the vendor account, then iterate the supplied catalogue and POST /products for each item.

Order-to-Shipment Sync

Push CS-Cart order events into a shipping platform and write tracking numbers back when labels are produced. The agent listens for new orders via GET /orders and posts each into the shipping platform, then updates /shipments/{id} on CS-Cart with carrier and tracking information once the label is generated. This keeps customer order pages live without manual data entry.

Call GET /orders for new orders, create shipments in the carrier platform, and PUT /shipments/{id} on CS-Cart with the tracking number.

AI Agent Storefront Operator

An AI agent acting as a merchandiser or support rep can run catalogue updates, resolve order queries, and update CMS pages through Jentic. The agent searches for the right CS-Cart operation across the 57-endpoint surface, loads its schema, and executes against the Basic auth credentials in the vault. The store admin retains audit attribution because every call goes through the configured admin user.

Search Jentic for 'update a CS-Cart order status', load the order update operation, and execute it with order_id and the new status value.

Key Endpoints

57 endpoints — the cs-cart api at version 2.

METHOD

PATH

DESCRIPTION

GET

/products

List products in the catalogue

POST

/products

Create a product

PUT

/products/{product_id}

Update a product

GET

/orders

List orders with filtering

GET

/orders/{order_id}

Retrieve order detail

GET

/users

List users

GET

/carts

Inspect in-progress carts

GET

/shipments

List shipments

GET

/products

List products in the catalogue

POST

/products

Create a product

PUT

/products/{product_id}

Update a product

GET

/orders

List orders with filtering

GET

/orders/{order_id}

Retrieve order detail

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

CS-Cart admin email, API key, and store domain are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens and never see the raw Basic auth pair.

Intent-based discovery

Agents search by intent (for example 'update an order status' or 'add a product to a category') and Jentic returns the matching CS-Cart operation with its input schema across the 57 endpoints.

Time to first call

Direct CS-Cart 2.0 integration: 2-3 days for auth, store URL templating, and operations across products, orders, and shipments. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify API

Hosted e-commerce platform with managed REST and GraphQL admin APIs

Choose Shopify when the merchant wants a hosted platform with managed scaling rather than a self-hosted CS-Cart deployment.

Alternative

Magento API

Open-source e-commerce platform with extensive B2B capabilities

Choose Magento when the workload needs richer B2B features such as company accounts and quotes that CS-Cart does not offer natively.

Complementary

Stripe API

Payments and subscription billing for e-commerce checkouts

Use Stripe alongside CS-Cart when the storefront's payment processor is Stripe and the agent needs to reconcile charges or refunds.

FAQs

Specific to using CS-Cart API API through Jentic.

What authentication does the CS-Cart API use?

CS-Cart 2.0 uses HTTP Basic authentication with the admin email as username and a generated API key as password. The base URL is templated against the store's own domain at /api/2.0. Through Jentic the credentials and domain are stored in the vault.

Can I update an order's fulfilment status with the CS-Cart API?

Yes. Call PUT /orders/{order_id} with the new status value. CS-Cart applies the configured status transitions, including notifications to customers if the status template is enabled.

What are the rate limits for the CS-Cart API?

CS-Cart does not publish an application-level request rate limit; capacity is governed by the host's PHP-FPM and database tuning. Spread bulk imports across off-peak windows and watch for slow responses as a backpressure signal.

How do I list orders for a specific customer through Jentic?

Search Jentic for 'list CS-Cart orders for a customer' and execute the loaded GET /orders operation with the user_id filter. Jentic supplies the Basic credentials and store domain from the vault.

Is the CS-Cart API free?

The API is included with every CS-Cart license at no extra per-call charge. CS-Cart sells annual and perpetual licenses with multiple editions; pricing is published at https://www.cs-cart.com/buy-license.html.

How do I add a new product to a category?

Call POST /products with a category_ids array including the target category, or call PUT /products/{product_id} on an existing product to add the category. The product appears on the category page on the next storefront request.