Next release: the chat bot's Playbook, FAQ and greeting#
- New permission:
bot:write. Keys with full access have it; a key or connection with chosen permissions needs it added (a new key, or reconnect and tick it). - New:
GET /v1/api/botreads the Playbook and the FAQ;POST /v1/api/bot/playbookreplaces the Playbook;POST /v1/api/bot/faqadds, updates or (withmode: "replace") removes questions. All writes takedry_run. See Update the chat bot's Playbook and FAQ. - Connector:
get_bot_playbook_and_faq,preview_playbook_update/apply_playbook_update,preview_faq_update/apply_faq_update. - New:
POST /v1/api/bot/greetingchanges the greeting new conversations on LINE, Facebook and Instagram open with: the text, then up to 10 videos, pictures or sets of product cards, each with an optionalmessagesent right after it.POST /v1/api/bot/greeting/mediauploads its videos and pictures.GET /v1/api/botanswers it asgreeting. API only for now. See Update the chat bot's Playbook, FAQ and greeting.
2026-10-30: product pictures#
- New: product rows in
POST /v1/api/products/upsert(and the connector's catalogue tools) takeimages: 1 to 7 picture links, copied onto SellerSideKick. See Add new products. - New:
POST /v1/api/imagesuploads pictures as files (multipart) and answers their links. GET /v1/api/productsanswers each product'simages.
Next release: feature a discount in the chat bot#
- New:
POST /v1/api/promotions/discountandPATCH /v1/api/promotions/discount/{id}takebot_feature: { enabled, announcement_th, announcement_en }(announcements up to 400 characters). While the discount runs, the shop's chat bot on LINE, Facebook, Instagram and web chat opens conversations with the announcement and recommends the discount's products first. Discounts read back with it. See Promotions. - New: bundles and BOGOs take
bot_featuretoo, and read back with it.
Next release: bigger promotion product lists#
- Changed: a promotion's product list (
product_discounts,applies_to.skus) now takes up to 5,000 SKUs, up from 500. It is sent whole in one request, because an update replaces the saved list. Product and stock writes stay at 500 rows per request.
Next release: a discount with a rate per product#
- New:
POST /v1/api/promotions/discountandPATCH /v1/api/promotions/discount/{id}takeproduct_discounts: [{ sku, discount_type, value }], a rate per SKU off every unit of it (up to 500 SKUs at first, 5,000 since), instead ofdiscount_type,valueandapplies_to. One promotion holds the whole sale, so it switches on and off at once. It reads back the same way it is written.
Next release: stock read-back and simpler variants#
- Fixed:
GET /v1/api/productsansweredstock: { on_hand: null, available: null }for every product. It now returns the counted and sellable numbers. - Variants: a new variant (
parent_sku) that gives nocategoryorbrandtakes the main product's. Anything the row gives still wins. - Clearer errors: a new product missing several required fields is told all of them at once, for example
A new product needs name, price and brand.
Permissions, key expiry and the AI-assistant connector#
- Connector at
https://mcp.sellersidekick.ai/mcpfor Claude, ChatGPT, Gemini Enterprise and Gemini CLI. You sign in with SellerSideKick and choose the shop and permissions. See Connect ChatGPT, Claude or Gemini. - Permissions on API keys:
catalog:read,catalog:write,stock:write,promotions:write. Existing keys and new keys default to full access. A call outside a key's permissions answers403 Y35. - Key expiry: never, 30, 90 or 365 days, with a reminder email 7 days before. An expired key answers
401 Y22. - Connected AI assistants are listed in Settings → API keys, each with a Disconnect button. Recent API changes there shows what keys and assistants changed, before and after.
- Change log in Settings → API keys: every change made through a key or an assistant, with the value before and after.
- These docs,
llms.txtand a Markdown copy of every page.
2026-10-25: OpenAPI spec 1.1.0 and usage counters#
- The OpenAPI spec is published at
https://api.sellersidekick.ai/v1/api/openapi.json, written for AI agents: when to call each operation, what to check first, whether a retry is safe, with examples. - Usage counters per key and per shop in Settings → API keys: calls, errors, rate-limited calls, dry runs and rows written, today and over the last 30 days.