> ## Documentation Index > Fetch the complete documentation index at: https://parabola.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # Connect Jitsu to Parabola > Pull Jitsu shipments, parcels, fees, POD, assignments, and tracking events into Parabola to automate last-mile delivery reporting, alerts, and reconciliation. Jitsu is a last-mile delivery platform used to plan, route, and track shipments from pickup through proof of delivery. Connecting Jitsu to Parabola lets ops teams centralize live tracking, delivery statuses, POD images and signatures, and fee data, so you can update customers, reconcile invoices, and keep internal systems in sync without copy-paste work. ## Pull from Jitsu The **Pull from Jitsu** step pulls data from your Jitsu account via the Jitsu API. It's a beta step built on top of Parabola's **Pull from an API** step, pre-configured to point at Jitsu and authenticate with a single API token. ## How to authenticate **Get your API token in Jitsu** * In your Jitsu dashboard, go to **API settings** and generate or copy your **API token**. * Store the token somewhere secure. **Connect in Parabola** * Add a **Pull from Jitsu** step to your flow. * 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. Parabola will include this Authorization header on every Jitsu request. ## Available data You can pull the following resources from Jitsu into Parabola: * **Shipments** — core shipment details, customer info, pickup and dropoff addresses and windows, service level, tags, internal references, tracking code and URL, timezone, workload, and computed display status. Includes flags like `asap`, `late`, `is_cancelled`, and options such as `signature_required` and `delivery_proof_photo_required`. * **Parcels (by shipment)** — itemized parcel rows with dimensions, weight, type (box, tote, etc.), 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 for 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 like `ASSIGNED`, `PICKUP_EN_ROUTE`, `DROPOFF_READY`, `DROPOFF_SUCCEEDED`, `DROPOFF_FAILED`, optional ETA values, next destination, driver remarks, and geo-coordinates. ## Common use cases * **Power live customer notifications**: Combine Jitsu tracking events with order data from [Shopify](/product/integration/shopify), [Squarespace](/product/integration/squarespace), or [Amazon Seller Central](/product/integration/amazon-seller-central) so customers get accurate "out for delivery" and "delivered" updates by email or SMS. * **Reconcile delivery fees against quotes**: Pull Jitsu fees and join them with carrier rate cards or invoices from [DHL](/product/integration/dhl), [FedEx](/product/integration/fedex), or [UPS](/product/integration/ups) to catch overcharges and missed adjustments before finance posts them. * **Attach proof of delivery to order records**: Pull POD images and signatures and push them into [NetSuite](/product/integration/netsuite), [QuickBooks Online](/product/integration/quickbooks-online), or [Smartsheet](/product/integration/smartsheet) so support teams have evidence ready for chargeback disputes. * **Trigger exception alerts**: Filter for `late`, `DROPOFF_FAILED`, or undeliverable signals and send a [Slack](/product/integration/slack) message or open a ticket in [Zendesk](/product/integration/zendesk) or [Gorgias](/product/integration/gorgias) for the ops team to triage. * **Build a single multi-region delivery view**: Union Jitsu shipments across warehouses with 3PL data from [ShipBob](/product/integration/shipbob), [ShipHero](/product/integration/shiphero), or [ShipStation](/product/integration/shipstation) into a single dashboard, then drop the result into [Google Drive](/product/integration/google-drive). * **Analyze driver and route load**: Aggregate assignments by driver and vehicle to balance daily routes and surface utilization trends to dispatch. ## Tips for using Parabola with Jitsu * **Normalize timestamps.** Jitsu returns ISO-8601 in UTC. Convert to your operating timezone before any SLA or "today" logic. * **Map raw signals to readable statuses.** Translate `DROPOFF_EN_ROUTE` to "Out for delivery" and similar before sending to customers or non-ops stakeholders. * **Keep tracking links handy.** Persist `tracking_url` with each shipment so you can drop a live tracking link into emails, portals, or support replies. * **Explode parcels for accurate analytics.** Each shipment can have multiple parcels with different weights and dimensions. Expand the parcel array before any per-parcel reporting or label generation. * **Match cadence to use case.** Every 15 minutes during delivery windows for live ops, daily for fee reconciliation, weekly for driver and route analysis. * **Persist key IDs.** Keep `shipment_id`, `tracking_code`, and any `internal_id` on every row to make future joins and updates easy. ## FAQ ### Can I push data back into Jitsu? The Pull from Jitsu step is read-only. To create or update shipments, use a **Send to an API** step pointed at the relevant Jitsu endpoint with your API token in the Authorization header. ### Why is my Authorization header failing? The header value must be the literal word `Token`, then a space, then the token itself, for example `Token abc123...`. Missing the word `Token` or the space is the most common cause of 401 errors. ### How do I pull tracking events for a specific shipment? Use the tracking events resource and pass the shipment's `tracking_code`. Pull shipments first to get the tracking codes, then pass them into a second step that fetches events per code. *** With Jitsu and Parabola connected, the customer updates, fee audits, and exception alerts your team handles by hand each day run on a schedule, with output landing in the systems where your team actually works.