Back
docs
Getting started

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.

Who this is for

Integration engineers
Technical builders
Building the API connection, implementing authentication, mapping data schemas, and deploying the integration to production.
Partner product and ops
Partner teams
Selecting the right integration path, understanding the surface ownership model, managing customers, and handling revenue share.

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.

PathWhat it deliversWho owns the surfaceEngagement product
Embedded APIPredictive intelligence signals via APIPartner’s own productNot included
White-LabelFull engagement platform under partner brandPartner-branded MustardHubOptional
Direct Link / SSOAttributed link into MustardHubMustardHub, partner-attributedIncluded

Start here

Most integration partners read the documentation in this order:

  1. Infrastructure overview: understand MustardHub’s underlying infrastructure before choosing how to deploy it.
  2. Glossary: familiarize yourself with MustardHub terminology.
  3. Integration Partner overview: compare the three paths and identify which fits your product and buyer profile.
  4. 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.

Uptime
99.9%
Monthly SLA
Breach notification
72 hrs
Partner notice
Change notice
30 days
Advance notification
Support
Dedicated
Partner success manager