{"pageKey":"Developers","slug":"developers","locale":"en-GB","localeResolved":"en-GB","fallbackApplied":false,"version":"developers@2026-10-07T20:57:15.681Z","lastModified":null,"canonicalUrl":"https://www.merchandaise.com/en-gb/developers","payload":{"slug":"developers","purpose":"llm-developers","title":"MerchandAise API & integration contracts | MerchandAise","description":"Explore MerchandAise contracts for assistant tooling, community embeds, supplier operations and enterprise identity, with clear public and protected access boundaries.","sections":[{"heading":"MerchandAise developer platform","paragraphs":["Connect a website, community, supplier operation or enterprise workspace to the same versioned design, quote, approval and order state. Start from the published contract, then plan access and the production rollout with us."]},{"heading":"What every integration must preserve","items":[{"title":"One versioned state","description":"Design, commerce intent, supplier-backed quote, approval and order status stay connected. Stale changes must trigger a visible re-quote or review state."},{"title":"Commercial and supplier privacy","description":"MerchandAise remains the buyer-facing merchant and support owner. Supplier identities, contacts and internal data are not exposed through public integrations."},{"title":"Approval before production","description":"A 3D view is not physical evidence. The confirmed quote explains any available customer-sample choices, costs, limitations, and timing. Approve the exact digital proof and complete mandatory technical checks and any required or selected sample approval before mass production. Existing accepted-order requirements remain binding."}]},{"heading":"API and integration surfaces","items":[{"title":"Assistant tooling API docs","description":"Explore current assistant and tooling endpoints for design sessions and integration review. This public reference does not grant anonymous authority to quote or place an order. 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 reference for assistant and tooling APIs. Production access and order-affecting operations still require the applicable authorization. Canonical section: /en-gb/developers#api-docs."},{"title":"Community embed API","description":"Connect localised club, community or storefront experiences to MerchandAise-owned design and commerce handoffs without rebuilding the underlying workflow. 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 versioned contract for storefront embeds, community discovery, and locale-aware handoffs. Canonical section: /en-gb/developers#community-integrations."},{"title":"Supplier API","description":"Connect approved suppliers to onboarding, catalogue, quote and fulfilment operations once the supplier relationship and access model are qualified. 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 contract for planning and client generation. Operational supplier access remains permissioned. Canonical section: /en-gb/developers#supplier-integrations."},{"title":"Enterprise identity API","description":"Plan SSO, SCIM provisioning and audit-ready identity flows for approved company merchandise programmes and governed rollouts. 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: /en-gb/developers#enterprise-integrations."},{"title":"MCP discovery and governed tools","description":"Use the public server card and external tools list for machine discovery, then honor each tool’s declared security, workspace, and confirmation boundaries when an agent executes it. Human guide: Read MCP implementation guide (/en-gb/developers/ai-agents-mcp). Machine-readable contract: Public MCP server-card JSON (/.well-known/mcp/server-card). Access: public. Public discovery document for machine clients. The external tools list at /api/v1/mcp/tools exposes current tool metadata; each tool call still follows its declared security, workspace, and confirmation boundaries. Canonical section: /en-gb/developers#mcp-tools."}]},{"heading":"Choose the contract before the code","items":[{"title":"Step 1: Map the user journey","description":"Decide who enters the workflow and where: a buyer in an embedded storefront, an approved supplier, an enterprise user, or an assistant operating with explicit authorisation."},{"title":"Step 2: Confirm the access boundary","description":"Use public contracts for evaluation and client generation, then confirm credentials, scopes, environments, callbacks and protected endpoints before implementation."},{"title":"Step 3: Prove state continuity","description":"Test that designs, quotes, approvals, errors and order handoffs remain version-current across the integration, including retries and rollback paths."}]},{"heading":"Before production traffic","paragraphs":["A published OpenAPI file is a planning surface, not a promise of anonymous production access. We review environments, credentials, failure handling and operational ownership before go‑live."],"items":[{"title":"Access and environments","description":"Confirm the contract version, approved workspace, authentication scopes, sandbox and production credentials, and callback destinations."},{"title":"Failure and recovery","description":"Define retries, idempotency, timeouts, customer-visible errors, observability, support ownership and rollback before release."},{"title":"End-to-end evidence","description":"Verify the intended journey in staging from entry and state mutation through quote, approval, handoff and recovery behaviour."}]},{"heading":"Bring us the workflow, not a finished architecture.","paragraphs":["Tell us who will use the integration, which state they need to read or change, and where the experience will live. We'll map the contract, access model and safest rollout path with you."],"items":[{"title":"Plan an integration","description":"/en-gb/contact?intent=api-integration-review"},{"title":"Explore AI agents and MCP","description":"/en-gb/developers/ai-agents-mcp"}]}],"source":{"type":"page-copy","id":"Developers"}},"metadata":{"source":"page-content","schema":"2025-11-05"}}