View All Docs

Pull from Jitsu

How to authenticate

Get your API token in Jitsu
- In your Jitsu dashboard, go to API settings and generate or copy your API token.
Connect in Parabola
- In Parabola, add a Pull from Jitsu step to the canvas.
- You’ll be prompted for a header called Authorization.
- Format matters: type the word Token, then a space, then paste your token.
  - Example: Token ofksldm9f834hgrefoids
- Save the connection.

That’s it—Parabola will include this Authorization header on all Jitsu requests.

You can pull the following data from Jitsu into Parabola:

Shipments: Core shipment details, customer info, pickup/dropoff addresses and windows, service level, tags, internal references, tracking code/url, timezone, workload, and computed display status. Includes flags like asap, late, is_cancelled, and options such as signature_required or delivery_proof_photo_required.
Parcels (by shipment): Itemized parcel rows with dimensions, weight, type (e.g., box, tote), and client parcel IDs.
Fees (by shipment): Delivery fee breakdowns, including base, pre-delivery, and post-delivery adjustments.
Labels: Shipment-level labels (PDF/ZPL/PNG) and parcel-specific labels with format and type options.
Proof of Delivery (POD): Time-stamped images and signature assets with secure URLs.
Assignments: Driver and vehicle details tied to an assignment (driver name, phone, profile photo; vehicle make/model, color, license plate) and the set of shipment IDs on the run.
Tracking Events (by tracking code): Time-sequenced events with signals (e.g., ASSIGNED, PICKUP_EN_ROUTE, DROPOFF_READY, DROPOFF_SUCCEEDED/FAILED), optional ETA values, next destination, driver remarks, and geo-coordinates.

Consolidate live delivery statuses and ETAs to power customer notifications.
Reconcile delivery fees (base and adjustments) against quotes or SLAs.
Pull proof-of-delivery (photos/signatures) and attach them to order records.
Monitor exceptions (late, failed, undeliverable) and trigger escalation workflows.
Build a single view of shipments across warehouses/regions with tracking links.
Analyze driver/vehicle assignment load to balance daily routes.

Normalize timestamps: Jitsu uses ISO-8601 timestamps (UTC). Convert to your operating timezone for SLA checks and dashboards.
Map statuses: Create a status mapping (e.g., DROPOFF_EN_ROUTE → “Out for delivery”) for clearer stakeholder updates.
Store tracking links: Keep tracking_url with each shipment so you can surface live tracking in emails or portals.
Automate exceptions: Filter for late/failed/undeliverable signals and send Alerts or route to a remediation queue.
Attach POD to orders: Join shipments to POD assets (images/signatures) and push to your order system or ticketing tool.
Schedule your flow: Run flows on a cadence (e.g., every 15 minutes during delivery windows; daily for fee reconciliation).
Keep parcel granularity: Explode parcel arrays for accurate weight/dimension analytics and label generation.
Document IDs: Persist shipment_id, tracking_code, and any internal_id to simplify future joins and updates.

Contents