Seekmodo

Seekmodo developer docs

Reference for the REST shim, MCP JSON-RPC surface, and storefront connectors. Authenticate with HMAC; replay window is 5 minutes.

Quick start

  1. Sign up and pick a plan at seekmodo.com/pricing.
  2. Pair your storefront with the connector for your platform — see the Connectors tab.
  3. Hit the gateway at https://mcp.seekmodo.com. Every authenticated request carries an HMAC envelope (see REST).

Surfaces

  • Connectors — install guides for Zen Cart, WordPress / WooCommerce, Magento, BigCommerce, and custom integrations. Deep pages (e.g. Zen Cart install, BigCommerce install, troubleshooting) live under each platform.
  • REST — drop-in compatibility shim. Same body shape as the underlying tools, just over plain JSON over HTTP.
  • MCP — JSON-RPC 2.0 at POST /. Implements tools/list and tools/call.
  • Sandbox — try requests live in your browser; we sign with a sample key server-side and stream the response.

SDK & headless storefronts

Sprint 7 shipped a public storefront SDK and a set of custom elements that consume it. Use these when you want to render search, recommendations, or chat directly in your storefront without writing the HMAC plumbing yourself.

  • SDKs — first-party clients for JavaScript / TypeScript, PHP, Python, Ruby, and Go. Browser storefronts use @seekmodo/sdk; server-side connectors use the language SDK that matches your stack. Start at the SDK hub.
  • Web Components — framework-agnostic <seekmodo-*> elements built on the SDK. Drop into any HTML page; styling via CSS variables and ::part.
  • Chat shopper — the conversational widget + the explicit "how chat-shopper meters" worked example merchants should sanity-check their /usage dashboard against.
  • Starters — reference Hydrogen + Astro repos wiring all of the above together against a public demo tenant.

Authentication

Get your tenant_id and shared secret at admin.seekmodo.com → Settings → Developer / API credentials. The connector handles HMAC signing for you; if you're calling the API directly, you'll copy the key from there. You can rotate the secret any time — old secrets stay valid for 10 minutes after rotation so connectors trailing on their 5-minute config refresh don't see a hard 401 cliff.

Send these four headers on every authenticated request:

  • X-Seekmodo-Tenant — your tenant id
  • X-Seekmodo-Timestamp — Unix timestamp (seconds)
  • X-Seekmodo-Nonce — random 16-byte hex string
  • X-Seekmodo-Signature — HMAC-SHA256 of <tenant>\n<timestamp>\n<nonce>\n<sha256(body)> using your shared secret.

See REST for the full request / response reference, rendered live from the OpenAPI 3.1 spec.