Community operators
Launch embedded storefronts, configurator handoffs, and community flows inside club, league, and company sites with versioned public contracts.
MerchandAise developer hub
Build merchandise into your product.
Connect your website, business systems or AI assistant to MerchandAise. Explore APIs for product design, community storefronts, supplier operations and company identity, with OpenAPI specifications and MCP documentation to guide your integration.
Who builds with MerchandAise
Enterprise teams and platform partners
Connect procurement portals, identity systems, and internal operations to merchandise workflows without rebuilding approval and supplier logic.
AI agent and automation builders
Give assistants structured tool access for discovery, quoting, and approved operations through MCP-compatible endpoints.
MerchandAise developer hub
Find your integration
01
API docs & OpenAPI
Find the API reference for assistant tooling and design sessions, then choose the community, supplier or enterprise contract for your workflow.
02
AI agents & MCP
Connect an AI assistant through the Model Context Protocol. Discover supported tools and preserve the user’s design choices, permissions and required confirmations.
Community API
Connect a club or community website to public community information, design submissions, voting and order approval handoffs.
Public versioned contract for storefront embeds, community discovery, and locale-aware handoffs.
Supplier API
Connect approved supplier systems to released production packages, onboarding status and ERP or PLM webhook workflows.
Public contract for planning and client generation. Operational supplier access remains permissioned.
Enterprise Identity API
Connect approved company workspaces to single sign-on, user and group provisioning, and identity audit records.
Protected contract for approved enterprise workspaces; request access before using this endpoint.
Explore enterprise identity
Enterprise identity OpenAPI JSON
01 — 03
Integration quickstart
01
Choose the contract that matches your workflow
Start with the surface that matches your user and auth model: community embed, enterprise identity, supplier operations, or MCP tools for assistants.
02
Validate auth, versioning, and environment boundaries
Confirm required headers, scopes, callback expectations, and contract versions in staging before you route production traffic.
03
Test end-to-end workflows before launch
Verify requests, webhooks, provisioning, observability, and rollback paths so the integration is reliable from first live usage.
What production-ready means
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.
01
Sandbox and access review
Confirm which contracts are public, which enterprise surfaces require approval, and which credentials or workspace roles are needed before launch.
02
Versioned implementation evidence
Keep generated clients, callback URLs, auth scopes, contract versions, and rollback ownership documented before production traffic is enabled.
03
Operational observability
Plan logs, retries, support ownership, failure states, and health checks for every workflow that can affect an order, supplier, or enterprise user.
Before you start building
Which MerchandAise API should I use?
Use the Community API for club and community website workflows, the Supplier API for approved supplier operations, and the Enterprise Identity API for company sign-in and provisioning. The API reference covers assistant tooling; the MCP guide explains how AI assistants discover and use supported tools.
Can I read the API specifications without an account?
The assistant tooling, Community and Supplier OpenAPI specifications are public. The Enterprise Identity specification is protected. Reading a public specification does not grant permission to execute protected requests or place orders.
Do I need a developer integration to order a product?
No. Individuals, clubs and companies can use the MerchandAise website to explore supported products and request a quote. APIs are an optional way to connect your own systems or experience.
What should I include in an integration request?
Describe who will use it, the systems involved, the information you need to read or update, and your intended timeline. Include sign-in, environment and callback requirements if known. The team reviews the appropriate contract and access model with you.
Need an integration review?
Share your architecture, rollout timeline, and destination channels. We will recommend the right contract surface, auth pattern, and launch sequence.