Skip to main content
Vendor-specific Connect documentation appears here as integrations ship.

​
Adding a vendor (internal)

Engineers onboarding a new Connect vendor should follow the 11-step playbook in qualifi-connectors/apps/standard-integration/docs/humanly-connect-vendor-playbook.md:
  1. Handlers in controllers/{vendor}/ (business logic)
  2. Mount /qsi/{vendor}/* for direct customers
  3. Copy connect/_template/ → connect/{vendor}/ for meta-routes + dual-mount
  4. Document here and in cURL examples
Key rule: one handler implementation, two URL prefixes (/qsi/* and /connect/*).

​
Available today

VendorNamespaceNotes
Stub/connect/stub/*Non-production smoke testing only. See Getting started.

​
Planned

VendorStatus
WorkdayPhase 2 (PLAT-85) — meta-routes + E2E
UKG, BambooHR, othersFuture vendor projects
Every vendor implements the same meta-routes contract before adding data routes.