REST · SDK · Webhooks · SSO
API, SDK and SSO integration
A large corporate programme usually does not live in a marketing tool. It lives in a procurement system, an expense workflow or a portal that somebody in IT maintains, and the merchandise order has to fit into that rather than the other way round. These pages describe how an integration is shaped: the endpoints, the events, the authentication and the single sign-on option for a client portal.
What an integration covers
The API surface. Creating a quote request, submitting a brief, reading order status and retrieving invoices are the operations a client system normally needs. Merchandise production is not a self-service catalogue, so the integration is deliberately narrow: it carries the brief and the status, not the artwork.
Webhooks. Polling a status endpoint is workable but wasteful and slow to react to. Events pushed on order confirmation, artwork approval, production start, dispatch and delivery remove the polling and let the client system update on its own schedule.
SSO for a client portal. Where a client wants its own staff to raise and track requests behind their own login, single sign-on removes a second password and a second user list. Authentication, entitlements and audit trail are designed together rather than bolted on.
Before an integration starts
- Who raises the order. A single named requester is easier to integrate than a general staff group.
- What the system owns. Whether quantities, cost centres and approvals live in the client system or in ours.
- Authentication. Credentials per environment, and how they are rotated.
- Event vocabulary. Agreed status names, because two systems rarely use the same words.
- Retry and failure. What happens when a webhook fails, and who is responsible for the retry.
- Timeline. Integration work is scheduled like production: it needs a start, a scope and a date.
Every integration page
Six pages covering the API, the SDK, webhooks and single sign-on.
What we are not
Corp-Merch.MX is an independent production workshop for corporate merch, uniforms and business gifting, invoicing to SAT under CFDI 4.0. The integration described here is a client system integration for raising and tracking orders; it is not a public software product or a platform sold to third parties. We are not an official partner, sponsor or approved supplier of any software vendor or identity provider named on this page.
Discuss an integration
Tell us which system the order has to reach, what it needs to send and what it needs back. We will come back with the scope, the dependencies and an honest estimate of what has to be true before a first release.