Integrations

DropScore connects to existing last-mile systems.

Ingest events from delivery workflows, compute explainable friction, and publish only operator-approved recommendations back to tenant-owned systems.

Tenant headers and idempotency Signed outbound webhooks Replay and exception handoffs
Inbound

Receive delivery events without changing tenant systems first.

Start with delivery, arrival, failure, contact-attempt, proof, package, and metadata events. Tenant headers and idempotency keys keep payloads scoped and replayable.

Operate

Turn integration health into operator work.

Surface missing events, failed auth, stale callbacks, dead letters, onboarding smoke status, and tenant remediation guides in the dashboard.

Outbound

Publish approved recommendations back to the tenant.

Use mock, signed webhook, export, API, or event bus patterns. DropScore records attempts, retries, dead letters, execution callbacks, and exceptions.

Inbound API

Delivery and event ingestion with tenant headers, idempotency keys, integration metadata, and audit records.

POST /integration/deliveries

Readiness checks

Tenant health, onboarding guides, smoke-run output, schema status, and pilot handoff reports.

GET /pilot/readiness

Outbound publishing

Mock or signed webhook handoff with retry, dead-letter, attempt history, and tenant execution reconciliation.

GET /outbound-actions

Tenant-owned systems stay in control.

DropScore can recommend extra pay, instruction repair, ETA adjustments, or safety review, but payroll, dispatch, customer messaging, and restrictions remain tenant-owned execution decisions.

Events in DropScore Approved actions out