For partners — attest activity on PTI
Partners
Verified activity in → portable trust out — one partner ID, the purposes (trust contexts) you enable, connectors that fit how you already operate.
Audience: commerce, telco, lending, and utility organizations that attest activity into PTI — and VAS / multi-bank integrators that fan out one integration across separately onboarded clients.
Register: choose Attest activity on Join TumiTrust (path id attest). Institutions that only look up trust choose Decide with trust (decide). People choose I am the subject (subject).
Your systems already know real activity. As a partner you send that activity into TumiTrust; the platform turns it into purpose-scoped, explainable outcomes that institutions can look up on the same network. Usage for ingest and compute is metered — see Partner billing when you are ready for commercial detail.
Integrators: see the Integrator guide for single-key fan-out (X-Client-Partner-Id), rail channel / program fields, and Add client in Embed Studio.
Outcomes
- Configure ingest (webhook, API, CSV) and your event catalog
- Enable the trust contexts (purposes) your contract covers
- Monitor health in Pulse and Partner Operations
- Understand usage and invoices when billing is live
Partner pipeline
You use the same institution hub as report consumers, plus producer surfaces: Partner operations, Connector, Data upload studio, and Pulse.
Start here
| I want to… | Guide |
|---|---|
| Configure webhooks, catalog, credentials | Connector configuration |
| Bulk-upload historical events (CSV) | CSV data upload studio |
| Enable multiple trust contexts (all documented IDs) | Trust contexts for producers |
| Understand TCU and invoices | Partner billing |
| Explore API contracts | OpenAPI at tumitrust.com/api/docs/ |
| Register | Trust producer signup |
Producer journey
Register ──► Onboard (contexts + partner ID) ──► Event catalog ──► Connector live
│
┌───────────────────────────────┼───────────────────────────────┐
▼ ▼ ▼
Webhook ingest CSV upload studio API / sync
│ │ │
└───────────────────────────────┴───────────────────────────────┘
▼
Pulse + Partner operations
(health, TCU, Insight Studio)
Hub mode
When your tenant links to an active partner profile, the console shows producer widgets:
| Widget | What you see |
|---|---|
| Data connection status | Connector health, last sync |
| Activity received today | Trust events by channel (webhook, CSV, API) |
| Entities onboarded | Subjects linked to PTI-IDs |
| Usage this period | TCU, USD estimate, forecast, per-context breakdown |
Console map
| Surface | In your hub | Purpose |
|---|---|---|
| Dashboard | Institution home | Executive snapshot |
| Pulse | Trust intelligence | Charts, Insight Studio, context filter |
| Partner operations | Sidebar → Partner operations | Ingest funnel, usage, timeline, catalog |
| Data upload | Partner operations → Data upload | CSV studio (validate → confirm → batch) |
| Connector | Partner operations → Connector | Webhook, delivery, policy, credentials |
| PTI network | Sidebar → PTI network | Platform network view |
Sidebar: Operations section groups Partner operations, Data upload, and PTI network.
Trust contexts
TumiTrust documents 20+ trust contexts — 10 primary life-area scopes and 10 lens cross-cutting views. Producers enable the primaries they emit; consumers request allowed contexts when generating reports.
One partner ID per organization; many contexts on one connector. See Trust contexts for producers for the full ID table and configuration API.
Ingest channels
| Channel | Guide section |
|---|---|
| Webhook | Connector configuration → first event |
| CSV batch | CSV data upload studio |
| API / connector | Connector configuration |
All channels tag events with context and source for Pulse and TCU attribution.
Confirmations (what “done” looks like)
| Milestone | How to confirm |
|---|---|
| Contexts enabled | GET …/api/partner/trust-contexts/ shows is_enabled: true |
| Catalog ready | Event catalog preview returns expected signals |
| Webhook live | Partner operations activity ↑; Insight Studio shows processed |
| CSV batch | Batch status completed; Pulse link opens filtered events |
| Billing | TCU breakdown shows context + operation rows |
Partner Operations (live console)
| Panel | Purpose |
|---|---|
| Identity & links | PTI-IDs, partner entity ids |
| Connector health | Status, errors |
| Ingestion funnel | Webhook vs CSV vs API by context |
| TCU dashboard | Period usage, forecast, invoices |
| Event feed | Pipeline stages per trust event |
Metrics poll: GET /institution/<slug>/api/partner-operations/metrics/
Pulse & Insight Studio
Pulse is the producer command center — TCU timelines, context radar, ingest charts.
Insight Studio filters events by date, sentiment, status, and context. After CSV ingest, open Pulse from the batch result link to audit rows by batch_id.
Consumer institutions use a separate Lookup Studio on trust reports — see For institutions.
Billing
Postpaid TCU metering with per-context visibility. Details: Partner billing.
Hybrid tenants
Some organizations produce and consume trust (e.g. bank + data affiliate). Hub mode hybrid shows both producer widgets and consumer report tools.
API & OpenAPI
Machine-readable contracts: tumitrust.com/api/docs/ (OpenAPI).
Support
Create live API keys after account verification, configure your event catalog in Partner Operations, and adjust contract tiers in Billing.