{"pageKey":"Developers","slug":"developers-api-integrations","locale":"en-US","localeResolved":"en-US","fallbackApplied":false,"version":"developers-api-integrations@2026-07-21T09:39:17.914Z","lastModified":"2026-07-21T09:39:17.914Z","canonicalUrl":"https://www.merchandaise.com/en-us/developers/api-integrations","payload":{"slug":"developers-api-integrations","purpose":"llm-developers-api-integrations","title":"Merchandise 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":"Keep one source of truth","paragraphs":["An integration should extend the MerchandAise workflow, not fork it. Website, embed, supplier, enterprise, and future assistant surfaces must read and update the same versioned design, commerce intent, quote, approval, and order state.","Where MerchandAise processes the buyer transaction, Hutter Products GmbH is the contracting seller and Merchant of Record under the MerchandAise brand. Supplier identity and contact details stay private except where disclosure is required, and production still requires digital-proof and genuine-sample approval."]},{"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: Read assistant tooling docs (/api/docs). 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 page: /developers/api-integrations. Canonical section: /developers/api-integrations#api-docs."},{"title":"Community embed API","description":"Connect localized club, community, or storefront experiences to MerchandAise-owned design and commerce handoffs without rebuilding the underlying workflow. Human guide: Review community integration guide (/en-us/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 page: /developers/api-integrations. Canonical section: /developers/api-integrations#community-integrations."},{"title":"Supplier API","description":"Connect approved suppliers to onboarding, catalog, quote, and fulfillment operations after the supplier relationship and access model are qualified. Human guide: Review supplier integration guide (/en-us/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 page: /developers/api-integrations. Canonical section: /developers/api-integrations#supplier-integrations."},{"title":"Enterprise identity API","description":"Plan SSO, SCIM provisioning, and audit-ready identity flows for approved company merchandise programs and governed rollouts. Human guide: Review enterprise integration guide (/en-us/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 page: /developers/api-integrations. Canonical section: /developers/api-integrations#enterprise-integrations."}]},{"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 authorization."},{"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 stay version-current across the integration, including retries and rollback paths."}]},{"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 product-native 3D view and digital proof support the decision, but they do not replace the genuine production sample required before mass production."}]},{"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, 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 behavior."}]},{"heading":"FAQ","items":[{"title":"Which integration surface should I start with?","description":"Start with the person and state transition. Use community embeds for buyer-facing club or community journeys, supplier operations for approved supply-side workflows, enterprise identity for SSO and SCIM, and assistant tooling only for explicitly authorized AI-led flows."},{"title":"Does a public contract mean public production access?","description":"No. A public OpenAPI contract supports discovery, architecture review, and client generation. Production credentials, write operations, supplier workflows, enterprise identity, and assistant execution can still require an approved workspace and scoped authorization."},{"title":"Can an integration expose suppliers or bypass approvals?","description":"No. Supplier identity and contact details remain private except where disclosure is required, MerchandAise owns the buyer relationship, and order-affecting actions must preserve the configured approval and genuine-sample gates."}]},{"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 will map the contract, access model, and safest rollout path with you."],"items":[{"title":"Plan an integration","description":"/en-us/contact?intent=api-integration-review"},{"title":"Explore AI agents and MCP","description":"/en-us/developers/ai-agents-mcp"}]}],"source":{"type":"page-copy","id":"Developers"}},"metadata":{"source":"page-content","schema":"2025-11-05"}}