{"pageKey":"Developers","slug":"developers","locale":"en-GB","localeResolved":"en-GB","fallbackApplied":false,"version":"developers@2026-03-20T08:14:54.764Z","lastModified":"2026-03-20T08:14:54.764Z","canonicalUrl":"https://www.merchandaise.com/en-gb/developers","payload":{"slug":"developers","purpose":"llm-developers","title":"Developer API, embeds, MCP tools & enterprise integrations | MerchandAise","description":"Explore MerchandAise developer APIs for custom merchandise: OpenAPI docs, community embeds, supplier workflows, enterprise identity, and MCP tools for AI agents.","sections":[{"heading":"Developer platform","paragraphs":["Use MerchandAise APIs, OpenAPI contracts, community embeds, supplier workflows, enterprise identity, and MCP tools to connect custom merchandise into websites, portals, and AI agents."]},{"heading":"Who builds with MerchandAise","items":[{"title":"Community operators","description":"Launch embedded storefronts, configurator handoffs, and community flows inside club, league, and company sites with versioned public contracts."},{"title":"Enterprise teams and platform partners","description":"Connect procurement portals, identity systems, and internal operations to merchandise workflows without rebuilding approval and supplier logic."},{"title":"AI agent and automation builders","description":"Give assistants structured tool access for discovery, quoting, and approved operations through MCP-compatible endpoints."}]},{"heading":"Integration surfaces and contracts","items":[{"title":"Assistant tooling API docs","description":"Read the assistant/tooling OpenAPI docs that support design sessions, tool use, and integration reviews. Community, supplier, and enterprise contracts are listed separately. Human guide: Open assistant tooling docs (/en-gb/developers/api-integrations). Machine-readable contract: Assistant tooling OpenAPI JSON (/api/docs/openapi.json). Access: public. Public machine-readable OpenAPI for assistant/tooling APIs; use the domain-specific contracts below for community, supplier, and enterprise implementation. Canonical section: /developers#api-docs."},{"title":"Community embed API","description":"Implement locale-safe storefront embeds, community workflows, and authenticated handoffs with a versioned public contract. Human guide: Review community integration guide (/en-gb/developers/api-integrations#community-integrations). Machine-readable contract: Community OpenAPI JSON (/api/v1/community/public/openapi/v1). Access: public. Public contract for storefront embeds, community discovery, and locale-aware handoffs. Canonical section: /developers#community-integrations."},{"title":"Supplier API","description":"Connect onboarding, catalog, and supplier-side operations through versioned endpoints built for fulfillment workflows. Human guide: Review supplier integration guide (/en-gb/developers/api-integrations#supplier-integrations). Machine-readable contract: Supplier OpenAPI JSON (/api/v1/supplier/openapi/v1). Access: public. Public versioned contract for supplier onboarding, catalog, and fulfillment workflows. Canonical section: /developers#supplier-integrations."},{"title":"Enterprise identity API","description":"Integrate SSO, SCIM provisioning, and audit-ready identity flows for enterprise rollouts and governance through a protected contract for approved enterprise access. Human guide: Review enterprise integration guide (/en-gb/developers/api-integrations#enterprise-integrations). Machine-readable contract: Enterprise identity OpenAPI JSON (/api/v1/enterprise/identity/openapi/v1). Access: protected. Protected contract for approved enterprise workspaces; request access before using this endpoint. Canonical section: /developers#enterprise-integrations."},{"title":"MCP server card and authorized tools","description":"Plan AI-agent integrations on the browser-safe MCP guide page, use the AI custom product designer pillar for intent-to-product context, then use the public server-card JSON for machine discovery and assistant-authorized endpoints for tool listing and execution. Human guide: Read MCP implementation guide (/en-gb/developers/ai-agents-mcp). Machine-readable contract: Public MCP server-card JSON (/en-gb/.well-known/mcp/server-card). Access: public. Public discovery document for machine clients. The tools list and tool execution endpoints still require assistant authorization at /api/v1/mcp/tools. Canonical section: /developers#mcp-tools."}]},{"heading":"Integration quickstart","items":[{"title":"Step 1: Choose the contract that matches your workflow","description":"Start with the surface that matches your user and auth model: community embed, enterprise identity, supplier operations, or MCP tools for assistants."},{"title":"Step 2: Validate auth, versioning, and environment boundaries","description":"Confirm required headers, scopes, callback expectations, and contract versions in staging before you route production traffic."},{"title":"Step 3: Test end-to-end workflows before launch","description":"Verify requests, webhooks, provisioning, observability, and rollback paths so the integration is reliable from first live usage."}]},{"heading":"Production launch gates for developers","paragraphs":["A production integration needs more than a public endpoint. Use these gates to decide whether your workflow is ready for customer, supplier, enterprise, or AI-agent traffic."],"items":[{"title":"Sandbox and access review","description":"Confirm which contracts are public, which enterprise surfaces require approval, and which credentials or workspace roles are needed before launch."},{"title":"Versioned implementation evidence","description":"Keep generated clients, callback URLs, auth scopes, contract versions, and rollback ownership documented before production traffic is enabled."},{"title":"Operational observability","description":"Plan logs, retries, support ownership, failure states, and health checks for every workflow that can affect an order, supplier, or enterprise user."}]},{"heading":"Need an integration review?","paragraphs":["Share your architecture, rollout timeline, and destination channels. We will recommend the right contract surface, auth pattern, and launch sequence."],"items":[{"title":"Talk to integrations team","description":"/en-gb/contact?intent=developer-integration-review"},{"title":"Explore enterprise platform","description":"/en-gb/enterprise"}]}],"source":{"type":"page-copy","id":"Developers"}},"metadata":{"source":"page-content","schema":"2025-11-05"}}