PrestaShop

Manage PrestaShop catalog, pricing, orders, customers, and stock through Webservice

Connect PrestaShop when a project needs data from an existing PrestaShop store. Swarmz uses the store's Webservice API, including its filters, field selection, JSON reads, and XML writes. The connection works in AI chat while you build and in a published app linked to it.

A Swarmz administrator must make PrestaShop visible before a workspace can connect it. No OAuth application is required. Each workspace supplies a Webservice API key from its own PrestaShop back office.

Before you connect

In the PrestaShop back office, open Advanced Parameters > Webservice. Enable Webservice, create a 32-character key, and grant only the resources and methods the project needs.

Common resources are products, categories, orders, customers, and stock_availables. Read-only dashboards need GET. Catalog, customer, order, or stock changes also need the matching POST or PATCH permission.

Copy the store's public HTTPS URL. Include its subdirectory, such as https://shop.example.com/prestashop, but don't add /api, a query string, or a fragment.

See PrestaShop Webservice access and the PrestaShop resource reference for provider permissions and fields.

Available operations

Area	Read operations	Write operations	Limit per minute
Products	`list_products`, `get_product`	`create_product`, `update_product`	30 read, 10 write
Categories	`list_categories`, `get_category`	`create_category`, `update_category`	30 read, 10 write
Orders	`list_orders`, `get_order`	`update_order`	30 read, 10 write
Customers	`list_customers`, `get_customer`	`create_customer`, `update_customer`	30 read, 10 write
Stock availability	`list_stock`	`update_stock`	30 read, 10 write

List operations accept PrestaShop query fields such as display, filter[...], sort, and limit. Swarmz adds output_format=JSON to reads and rejects attempts to replace it. Queries contain at most 32 fields. Request bodies are limited to 128 KB and responses to 2 MB.

PrestaShop writes use XML. The AI sends a bounded field tree and Swarmz escapes its text and attributes before it builds the XML document. A multilingual product name can use this shape:

{
  "fields": {
    "name": {
      "language": [
        {
          "_attributes": { "id": 1 },
          "_text": "Trail shoe"
        }
      ]
    },
    "price": "89.00",
    "active": true
  }
}

Object keys become XML elements. Arrays repeat an element. _attributes sets XML attributes and _text sets the element text. Swarmz rejects invalid XML names, control characters, excessive depth, and oversized trees.

Connect PrestaShop

In Settings > Integrations, select PrestaShop, then select Connect new.
Enter a name that identifies the store or environment.
Enter the public HTTPS Store URL, including any PrestaShop subdirectory.
Enter the 32-character Webservice API key in the secure form.
Link the connection to the project when the AI requests it.

Credential validation reads one product from /api/products. If it fails, open that route through the PrestaShop Webservice test tool and check that the key has GET permission for products.

Build with PrestaShop

Describe the store view and the changes the app should permit. For example:

“Use PrestaShop to build an operations dashboard with recent orders, revenue, fulfillment status, and low-stock products.”
“Build a catalog editor that searches products, edits prices, and shows their categories.”
“Create a support view that searches customers and shows their recent orders.”
“Build an inventory monitor that filters stock_availables by product and updates the selected quantity.”

The AI requests the PrestaShop connection before it adds the first server-side operation. It can use only the resources and HTTP methods granted to the Webservice key.

Test PrestaShop

Use a staging store or disposable records for write tests.

List products with display=[id,name,price] and limit=0,1. Confirm the returned record in the PrestaShop back office.
Create a disabled test product, update its price, and confirm both values in the catalog.
Create a test category and assign it to the disposable product.
List customers and orders with a narrow filter[...], then open the matching records in the back office.
Read the product's stock_available record, update its quantity, and confirm the stock change.
Delete or disable the disposable records in PrestaShop after the checks pass.

If reads work and one resource fails, add GET permission for that resource to the key. If writes fail, add the required POST or PATCH permission and reconnect. PrestaShop keys don't rotate automatically. Revoke an exposed key in the back office before entering its replacement in Swarmz.