Obtain your API token and key from the Constructor dashboard. Catalog items are ingested via the Catalog Management API; send a PATCH /v1/catalog request with a multipart body containing CSV or JSON files for items, variations, and item groups, plus a section parameter (typically 'Products').
For delta updates, set the type parameter to delta to update only changed records; for a full replacement use type=full. Constructor processes ingestion jobs asynchronously — poll the Tasks API (GET /v1/tasks/{task_id}) to confirm completion.
Query autocomplete suggestions by calling GET https://ac.cnstrc.com/autocomplete/{term}?key=YOUR_KEY&num_results=10§ion=Products; the response contains suggestion groups including 'Search Suggestions' and 'Products'.
Query full-text search by calling GET https://ac.cnstrc.com/search/{term}?key=YOUR_KEY&page=1&num_results_per_page=20; apply filters via the filters[field]=value query parameter.
Send behavioral events (click, conversion, search) back to Constructor using the Events API (POST /v1/behavioral_action/click, etc.) with the user's session identifier so the model can personalise results over time.
Known gotchas
The key query parameter is your public API key (safe for client-side use); separate admin API tokens are used for catalog ingestion and should remain server-side only.
Full ingestion (type=full) replaces the entire catalog section; if a product is missing from the file it will be removed. Use delta ingestion for routine updates.
As of January 2026 Constructor introduced Discoverable Collection Items — if you use Collections, verify your API client version supports the latest Collection Creation API enhancements.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp