Integration partner documentation.
This documentation is for technical partners and integration engineers building on top of MustardHub, embedding it into existing products, or deploying it for their customers.
What this covers
INTEGRATION PARTNER covers the three deployment paths available to partners: path selection, integration mechanics, the credential and tenant model, and everything needed to execute an integration. GETTING STARTED (this section) and RESOURCES provide orientation and reference.
Three architectural paths for how your product exposes MustardHub to your customers: Embedded API, White-Label, and Direct Link / SSO.
The intelligence layer, behavioral models, credential model, and engagement engine that power every integration path.
Who this is for
Three partner paths, one infrastructure
All partner integrations run on the same underlying infrastructure, which includes the same intelligence layer, the same behavioral models, the same security posture, and the same credential model. The three paths differ in what they expose to customers and who owns the surface. The full engagement surface and workspace account architecture are included in White-Label and Direct Link / SSO; Embedded API delivers intelligence signals only, with no customer-facing engagement layer.
| Path | What it delivers | Who owns the surface | Engagement product |
|---|---|---|---|
| Embedded API | Predictive intelligence signals via API | Partner’s own product | Not included |
| White-Label | Full engagement platform under partner brand | Partner-branded MustardHub | Optional |
| Direct Link / SSO | Attributed link into MustardHub | MustardHub, partner-attributed | Included |
Start here
Most integration partners read the documentation in this order:
- Infrastructure overview: understand MustardHub’s underlying infrastructure before choosing how to deploy it.
- Glossary: familiarize yourself with MustardHub terminology.
- Integration Partner overview: compare the three paths and identify which fits your product and buyer profile.
- The relevant path page: Embedded API, White-Label, or Direct Link / SSO.
Shared foundations
Every integration path runs on the same security posture, the same partner-scoped credential model, and the same operational commitments. The standard is documented in the Security and operations section on each path page.