{"pageKey":"Developers","slug":"developers-api-integrations","locale":"en-GB","localeResolved":"en-GB","fallbackApplied":false,"version":"developers-api-integrations@2026-03-20T08:14:54.764Z","lastModified":"2026-03-20T08:14:54.764Z","canonicalUrl":"https://www.merchandaise.com/en-gb/developers/api-integrations","payload":{"slug":"developers-api-integrations","purpose":"llm-developers-api-integrations","title":"API and integrations for custom merchandise | MerchandAise","description":"Use MerchandAise API and integration pages for assistant tooling docs, community embeds, supplier workflows, enterprise identity, and production launch planning.","sections":[{"heading":"What this page covers","paragraphs":["This is the crawlable entry point for teams evaluating MerchandAise API and integration work. It separates implementation guides from machine contracts so developers, search engines, and AI assistants can cite the right surface.","Use it when you need assistant tooling docs, storefront embeds, supplier operations, enterprise identity, or a versioned OpenAPI contract before moving into implementation."]},{"heading":"API and integration surfaces","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: Read assistant tooling docs (/api/docs). 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 page: /developers/api-integrations. Canonical section: /developers/api-integrations#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 page: /developers/api-integrations. Canonical section: /developers/api-integrations#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 page: /developers/api-integrations. Canonical section: /developers/api-integrations#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 page: /developers/api-integrations. Canonical section: /developers/api-integrations#enterprise-integrations."}]},{"heading":"Production implementation checklist","items":[{"title":"Step 1: Choose the right contract surface","description":"Match the integration to the user journey first: community embeds for public storefronts, supplier APIs for fulfillment workflows, and enterprise identity for SSO, SCIM, and governed rollouts."},{"title":"Step 2: Generate and test against versioned contracts","description":"Use the published OpenAPI JSON for client generation, contract review, staging validation, and regression testing before production traffic is enabled."},{"title":"Step 3: Confirm access, callbacks, and rollback paths","description":"Document authentication scopes, callback URLs, environment boundaries, observability, and rollback ownership before launch."}]},{"heading":"Production safeguards","items":[{"title":"Clear contract ownership","description":"Each integration surface links to an implementation guide and the machine-readable contract separately, reducing ambiguity during implementation and reviews."},{"title":"Locale-safe discovery","description":"The page is localized, included in locale sitemaps, and linked from global navigation so teams and search engines can discover it directly."},{"title":"Access boundaries","description":"Public contracts are linked directly. Protected enterprise and assistant-authorized contracts are described without implying anonymous production access."}]},{"heading":"Before this API integration goes live","paragraphs":["Use this checklist to turn the public contracts into a supported integration plan with clear access, rollout, and rollback ownership."],"items":[{"title":"Request sandbox and credential review","description":"Route your use case through integrations review so public, supplier, and protected enterprise surfaces are scoped correctly."},{"title":"Document auth and callback boundaries","description":"Record required scopes, callback URLs, environment names, webhook ownership, and customer-visible failure handling."},{"title":"Verify contract health before release","description":"Check OpenAPI JSON, protected access behavior, staging requests, and monitoring alerts before the first production handoff."}]},{"heading":"FAQ","items":[{"title":"Which MerchandAise API should I start with?","description":"Start with the surface that matches the user journey: community embeds for storefront experiences, supplier APIs for fulfillment workflows, and enterprise identity APIs for SSO or SCIM rollouts."},{"title":"Are the API contracts public?","description":"Assistant tooling, community, and supplier OpenAPI contracts are public. Enterprise identity and MCP tools-list contracts are protected and require approved access before use."},{"title":"Can AI assistants use this page?","description":"Yes. The page exposes a dedicated LLM feed, canonical metadata, structured data, and stable links to human guides and machine-readable contracts."}]},{"heading":"Need an integration review?","paragraphs":["Share the workflow, target environment, authentication needs, and launch timeline. The integrations team will recommend the correct contract surface and rollout path."],"items":[{"title":"Talk to integrations team","description":"/en-gb/contact?intent=api-integration-review"},{"title":"View 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"}}