Partner Integration Guide
Business integration
For partnership and BD teams — not a replacement for technical connector docs.
Who this is for
Trust producers — commerce platforms, lenders, telcos, HR systems — that emit signals into PTI.
Technical detail: Connector configuration · CSV upload · Trust contexts
Integration timeline (typical)
| Week | Milestone |
|---|---|
| 1 | Partner profile + enabled contexts |
| 2 | Event catalog + test webhook or CSV |
| 3 | Pulse validation + TCU visibility |
| 4 | Production ingest + billing alignment |
Complexity scales with context count and channel mix.
What partners send
- Events with
context_id,event_type, subject reference (pti_idor mapped ID) - Single-context CSV batches for bulk backfill
- Webhook payloads signed per connector policy
What partners receive
- PTI-ID mapping for onboarded entities
- TCU usage per context (month-to-date in hub API)
- Ingest validation errors with clear context policy messages
Webhooks (two directions)
| Direction | Meaning | Contract |
|---|---|---|
| Partner → TumiTrust | You send trust events | POST /api/v1/partner/webhooks/{partner_id}/ + X-Partner-Signature — Connector configuration |
| TumiTrust → Partner | We deliver report / signal notifications | Register under /api/v1/trust-signals/webhooks/ and verify X-Webhook-Signature — Trust Platform API — Webhooks |
Commercial model
- Postpaid TCU (Trust Compute Units) for ingest and compute
- Context-level attribution on invoices where supported
- See Partner billing
SLAs & support
- Ingest acceptance: real-time validation feedback
- Uptime: Status page
- Escalation via institution hub Support and in-app help
Pilot process
- Enable sandbox connector on tumitrust.com
- Send test events for one primary context (often
merchantorlending) - Confirm Pulse charts and TCU rows
- Promote to live ingest by enabling your production connector in Partner Operations