Developer Lab · Nexus
Build one adapter. Reach every operation that needs it.
Nexus is the integration fabric beneath TruckerTech. You translate your API to one set of versioned canonical schemas; Nexus governs every exchange and runs the hard parts once, for everyone.
What you build
A manifest, an adapter package and a conformance run.
That is the whole cost of a new partner. Adding, certifying, limiting or disabling a partner changes data, not the platform, so breadth grows with partners rather than with our engineering headcount.
Manifest
Declare what you serve
A versioned document listing your capability sockets, their purposes, your auth strategy, limits and event model. No field can hold a credential.
Adapter
Translate, and nothing more
Provider DTOs, request builders, mappers to canonical schemas, and status and error mapping, built on the adapter SDK. It returns values; it writes nothing and decides nothing about authority.
Conformance
Prove it in the sandbox
The kit exercises your adapter against a synthetic operating world with a deterministic clock and no network, so a result is reproducible evidence.
What Nexus does for you
The hard parts run once, in the platform, for every partner and every customer.
Governs before it invokes
Identity, authority, purpose, data rights, source authority and entitlement are settled before your adapter runs. Your adapter receives an already-scoped request.
Runs the hard parts once
Durable ingress, deduplication, ordering, retries, reconciliation, rate limits and circuit breakers live in the platform, not in every adapter.
Distributes your results
Normalized, attributed facts reach the workspace, Automation, Intelligence and the audit history through one path.
Keeps credentials out of reach
A connection holds a reference to hosted custody, never a value. Your adapter never sees a stored credential, another tenant or a database.
Guarantees
Four guarantees the fabric is built around.
Canonical in, canonical out
Adapters translate provider payloads to and from versioned canonical schemas. Your schema never enters TruckerTech, and TruckerTech never handles provider-shaped objects.
Acknowledgement is not confirmation
Every external effect runs an idempotent state machine with a deduplication key stored before anything is sent. “Accepted” and “done” are recorded separately, per destination.
Attribution survives
Provider identity, freshness and source class travel with every fact, including after reconciliation. Your results are never relabeled as TruckerTech’s.
Everything can be disabled
Per connection, per capability, per partner and per tenant, immediately and with evidence.
The manifest
Declare your capabilities. The platform does the rest.
An illustrative manifest for a fictional ELD provider: one adapter, two capability sockets. The SDK reference defines the exact schema.
// A fictional provider. One adapter, two sockets.
export const manifest = defineCapabilityManifest({
adapterId: 'example-eld',
adapterVersion: '1.3.0',
auth: { strategy: 'oauth_authorization_code' },
sockets: [
{
capability: 'eld.hos.duty_status',
capabilityClass: 'R', // read
canonicalSchema: 'eld-hos@1',
allowedPurposes: ['dispatch.hos_check'],
webhookSupported: true,
},
{
capability: 'eld.vehicle.location',
capabilityClass: 'E', // event
canonicalSchema: 'vehicle-position@1',
allowedPurposes: ['visibility.milestones'],
},
],
limits: { requestsPerMinute: 120, timeoutMs: 15_000 },
});- Every socket declares its purposes. A caller’s purpose must be on that list; Nexus never derives, widens or infers one.
- Bounded by construction. Timeouts and retry policies have hard ceilings, and the platform, not the adapter, retries.
- Refused at registration, before any traffic exists: duplicate identifiers, malformed adapters and undeclared capabilities.
- Versioned independently. A change to one provider endpoint never invalidates unrelated capabilities.
Adapter checklist
- No credential, key or token in code or configuration
- No retry loops, sleeps or timers in the adapter
- Every provider status mapped, or left unknown
- Provider timestamps carried as facts
- Acknowledgement and confirmation reported separately
- Commands send an idempotency key and an expected version
- Only the fields the capability needs are requested
- Telemetry carries codes and counts, never payloads
Partner lifecycle
Certification is earned per capability.
Each stage is recorded, and none requires a change to TruckerTech itself. A provider can be published capability by capability as each one passes; Nexus never claims a binary “integrated”.
Discovery
Map your product to capability sockets, classify each operation (read, event, workflow or financial) and write the manifest.
Sandbox
Build on the SDK and the canonical schemas, and run against a production-shaped synthetic operating world, with no network in tests.
Certification
A conformance kit runs per capability and writes a certification record. Production routing requires it, and the required cases rise with the class.
Production
Your system and capabilities are registered from the manifest. Customers discover you in context, activate you and bind their own account.
Suspend, disable or offboard at any level, immediately and with evidence. Removing a connection is as governed as adding one.
Capability sockets
The capabilities an adapter can serve.
One provider can serve many sockets, and one socket can have many eligible providers. Each socket family has a versioned canonical schema.
- Identity assurance
- Qualification and compliance
- Payments and factoring
- Scheduling and appointments
- Visibility and ETA
- TMS loads and orders
- ERP demand
- ELD, hours of service and telematics
- WMS, yard and dock
- Communications channels
- Documents and e-signature
- Driver recruiting
- Fuel and maintenance
- Load boards
- External AI (read-only)
- EDI (204, 990, 214, 210)
Every Core that depends on a capability a partner can serve also has a native flow, so an adapter adds depth and speed and is never a single point of failure for a customer.
For specialist providers
Your systems remain your systems. Your specialized services remain yours to deliver.
You keep your product, your customer relationship and your name. TruckerTech supplies the governed context, the permission and the record around your work, and shows whose answer it is.
- Partners specialize. TruckerTech does not recreate qualification, telematics, visibility, insurance, fraud, credit, factoring or maintenance products.
- Found where the need appears. Customers discover your capability in context, inside the work, and activate it themselves.
- Bring your API documentation and the sockets you want to serve; we will work through the manifest with you.