REST API

Platform REST mirrors MCP tools. Use it from backends, scripts, and automation. Native storefronts should use the Mobile app API instead — that path carries customer JWT, Bag sync, and assist mode.

• Commerce: GET /api/v1/platform/tools then POST /api/v1/platform/tools/{tool_name}
• Odoo Agent: GET /api/v1/platform/erp/tools then POST /api/v1/platform/erp/tools/{tool_name}

Send your workspace MCP API key as a Bearer token. Get it from the eCommerce Agent page. Never put this key in a public app or browser.

Authorization: Bearer YOUR_MCP_KEY
Content-Type: application/json

List tools, then POST JSON arguments. Example product search:

curl -X POST https://YOUR_HOST/api/v1/platform/tools/search_products \
  -H "Authorization: Bearer YOUR_MCP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"arguments":{"query":"acoustic panel","limit":5}}'

Optional customer_phone on the body scopes customer-specific tools. Cart and checkout tools still run as the tenant Odoo service user — not a shopper JWT.

ERP calls run as a specific Odoo user. Add that employee’s login and API key so ACLs match the UI.

curl -X POST https://YOUR_HOST/api/v1/platform/erp/tools/search_records \
  -H "Authorization: Bearer YOUR_MCP_KEY" \
  -H "X-Odoo-User-Login: your.odoo.login" \
  -H "X-Odoo-User-Token: YOUR_ODOO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"arguments":{"model":"crm.lead","limit":5,"fields":["id","name"]}}'

• 401 — missing or invalid MCP key
• 402 — plan or usage limit
• 404 — unknown tool

Machine-readable OpenAPI lives at /docs.