MerchandAise developer platform
Connect your workflow to MerchandAise.
Find API documentation and OpenAPI specifications for custom merchandise workflows. Connect websites, communities, supplier operations or company accounts to shared design, quote and order information.
Choose the connection your project needs
Use the references below to evaluate endpoints, request formats and authorization requirements. Public specifications support planning and client generation; operational access depends on the API, account and environment.
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 approval, confirmed producibility, mandatory technical checks, and the sample approvals applicable to the exact accepted order.
01 — Contracts
API and integration surfaces
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.
Implementation guide
Read assistant tooling docsMachine contract
Assistant tooling OpenAPI JSON/api/docs/openapi.jsonPublic reference for assistant and tooling APIs. Production access and order-affecting operations still require the applicable authorization.
02
Community API
Connect a club or community website to public community information, design submissions, voting and order approval handoffs.
- What the contract covers
- Public community context, design posts and votes, listing publication, pending orders, and community-owner approval or rejection.
- A practical starting point
- Read public community context for a club website. Then map which actions require a member session or owner permissions before adding design submissions or checkout handoffs.
- Access
- The specification is public. Public reads, member actions and owner-only operations have different authorization requirements; use the security rules on each endpoint.
Machine contract
Community OpenAPI JSON/api/v1/community/public/openapi/v1Public versioned contract for storefront embeds, community discovery, and locale-aware handoffs.
03
Supplier API
Connect approved supplier systems to released production packages, onboarding status and ERP or PLM webhook workflows.
- What the contract covers
- Supplier onboarding state, released production packages, audited artifact downloads, analytics, webhook subscriptions and sync checkpoints.
- A practical starting point
- Plan a connection between your ERP or product lifecycle management system and Supplier Center. Review webhook payloads, retries and sync status before handling an assigned order.
- Access
- Read the OpenAPI specification without signing in. Operational requests require the appropriate supplier account and permissions; public documentation does not enroll a supplier or grant access to another supplier’s data.
Machine contract
Supplier OpenAPI JSON/api/v1/supplier/openapi/v1Public contract for planning and client generation. Operational supplier access remains permissioned.
04
Enterprise Identity API
Connect approved company workspaces to single sign-on, user and group provisioning, and identity audit records.
- What the contract covers
- OpenID Connect (OIDC) single sign-on, SCIM user and group lifecycle operations, SCIM token rotation, and provisioning audit events.
- A practical starting point
- Map your identity provider to the approved workspace. Plan sign-in, user provisioning and deprovisioning, then verify group mappings and audit records in the agreed test environment.
- Access
- The enterprise identity specification is protected. Contact the integrations team to review the workspace and access requirements before implementation. Enterprise identity is optional for ordinary product purchases.
Machine contract
Enterprise identity OpenAPI JSON/api/v1/enterprise/identity/openapi/v1Protected contract for approved enterprise workspaces; request access before using this endpoint.
Plan an integration02 — Implementation guide
Choose the contract before the code
- 01
Map the user journey
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.
- 02
Confirm the access boundary
Use public contracts for evaluation and client generation, then confirm credentials, scopes, environments, callbacks, and protected endpoints before implementation.
- 03
Prove state continuity
Test that designs, quotes, approvals, errors, and order handoffs stay version-current across the integration, including retries and rollback paths.
03 — What every integration must preserve
What every integration must preserve
One versioned state
Design, commerce intent, supplier-backed quote, approval, and order status stay connected. Stale changes must trigger a visible re-quote or review state.
Commercial and supplier privacy
MerchandAise remains the buyer-facing merchant and support owner. Supplier identities, contacts, and internal data are not exposed through public integrations.
Approval before production
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.
04
Before production traffic
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.
Access and environments
Confirm the contract version, approved workspace, authentication scopes, sandbox, production credentials, and callback destinations.
Failure and recovery
Define retries, idempotency, timeouts, customer-visible errors, observability, support ownership, and rollback before release.
End-to-end evidence
Verify the intended journey in staging from entry and state mutation through quote, approval, handoff, and recovery behavior.
FAQ
Which merchandise API should I start with?
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.
Does a public contract mean public production access?
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.
Can an integration expose suppliers or bypass approvals?
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 digital-proof, technical, and order-specific sample approval requirements.
Plan your integration with us.
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.