Connect EasyPost to Parabola

Pull EasyPost shipments, trackers, rates, addresses, and SmartRate predictions into Parabola to automate carrier audits, delivery reporting, and rate shopping.

EasyPost is a multi-carrier shipping API that lets brands and 3PLs rate shop, buy labels, verify addresses, and track parcels across USPS, UPS, FedEx, DHL, and dozens of regional carriers through a single integration. Connecting EasyPost to Parabola lets shipping and ops teams pull tracker, rate, and shipment data into the same flows used for orders, invoices, and warehouse data, so carrier audits, on-time reporting, and rate-shopping logic run on a schedule.

Pull from EasyPost

The Pull from EasyPost step pulls data from EasyPost’s REST API. You can pull shipments, trackers, rates, addresses, and SmartRate delivery predictions, then join the results with order, fulfillment, or accounting data to drive reporting and alerts.

How to authenticate

EasyPost uses Basic Authentication with your API key as the username; no password is required.

1. Get your EasyPost API key. Log in to EasyPost and open Account Settings → API Keys. Click Add Additional API Key if you need a new one. EasyPost issues both Test and Production keys, use Production for live data.

2. Connect in Parabola. Add a Pull from EasyPost step to your flow, click Authorize, and paste your API key into the username field. Leave the password blank.

3. Pick the EasyPost endpoint you want, Shipments, Trackers, Addresses, Parcels, Rates, SmartRates, and run the step.

Parabola stores the credentials securely and uses them on every run.

Available data

EasyPost’s API exposes everything related to a parcel’s lifecycle. The most common endpoints operators pull:

• Shipments — shipment ID, from/to address, parcel dimensions and weight, selected rate, label URL, tracking code, status, options (signature, insurance), and timestamps.
• Trackers — tracking code, carrier, current status (pre_transit, in_transit, out_for_delivery, delivered, return_to_sender, failure), estimated delivery date, public tracking URL, and the full scan event log with timestamps and locations.
• Rates — every rate returned for a shipment, with carrier, service level, list price, retail price, your negotiated price, currency, delivery days, and a delivery date estimate.
• Addresses — name, company, full street address, city, state/region, ZIP/postal code, country, phone, email, and residential vs. commercial classification.
• Address verification — verified or corrected address output and any verification errors, useful for catching bad addresses before label purchase.
• Parcels — saved parcel templates with weight and dimensions for repeat shipments.
• Pickups — pickup requests with timing, address, and status.
• SmartRate — predicted transit time at the 50th, 75th, 85th, 90th, 95th, and 99th percentiles for each rate.
• SmartRate delivery dates — predicted delivery date for each rate based on a planned ship date.
• SmartRate precision shipping — recommended ship date per carrier and service level to hit a target delivery date, with delivery confidence scores.

Common use cases

• Audit carrier invoices: Join EasyPost shipment and rate records with carrier billing files from UPS, FedEx, or DHL to catch overcharges, surcharges, and duplicate billings before paying.
• Build a unified tracking feed: Pull EasyPost trackers and join with orders from Shopify, Amazon Seller Central, or Fulfil to give CX a single view of every parcel.
• Report on delivery performance and SLAs: Compare EasyPost tracker timestamps against promised delivery dates to measure on-time rate, transit days, and missed SLAs by carrier and lane.
• Rate-shop on a schedule: Pull EasyPost rates for a sample of upcoming shipments and feed them into a Slack digest or Google Drive sheet so your ops team sees the cheapest service for each lane each morning.
• Verify addresses before fulfillment: Run new orders through EasyPost address verification and route bad addresses to a CX queue or Slack channel before a label is ever bought.
• Push shipment data to accounting: Send EasyPost shipment costs and tracker outcomes into NetSuite or QuickBooks Online for clean shipping expense reporting at month close.
• Use SmartRate for high-stakes shipments: For time-sensitive orders, pull precision shipping data and pick the carrier and service with the highest delivery confidence for the customer’s required date.

Tips for using Parabola with EasyPost

• Use the Production key for live data. Test keys return mock responses, useful for building flows but not for reporting. Once you’re ready, swap in the Production key.
• Filter trackers to active shipments. Once a tracker is delivered or return_to_sender, you don’t need to keep pulling it. Add a Filter rows step on status to keep flows focused on parcels still in motion.
• Join on tracking_code, not id. The EasyPost tracker id is unique to EasyPost; the carrier tracking number (tracking_code) is what shows up in your OMS, ERP, or 3PL system. Use the tracking code as the join key.
• Pull rates and shipments together for audits. A shipment’s selected rate is what you’re billed; the full rate list is what you could have used. Joining the two surfaces missed savings.
• Use SmartRate percentiles deliberately. The 50th percentile is “typical” transit; the 95th and 99th show worst case. For “must arrive by Friday” reports, filter on the higher percentiles.
• Match cadence to use case. Hourly for active tracker pulls and CX dashboards, daily for delivery performance reporting, weekly for invoice audits and rate analysis.

FAQ

Can I buy EasyPost labels from Parabola?

The Pull from EasyPost step is read-only. To create shipments, buy labels, or schedule pickups, use a Send to an API step pointed at EasyPost’s shipments endpoint with your API key.

What’s the difference between Test and Production keys?

Test keys return mock responses without charging your account or talking to real carriers, useful for building flows. Production keys hit live carrier APIs and reflect real shipments. Don’t mix them in the same flow.

How do I pull only shipments from a specific date range?

Pull from the shipments endpoint and add a Filter rows step on created_at. For high-volume accounts, schedule the flow more frequently and filter to a narrow window so each run stays fast.

Can I pull from multiple EasyPost accounts in one flow?

Yes. Add a separate Pull from EasyPost step for each account and authorize each with its own API key, then union the outputs downstream.

---

With EasyPost and Parabola connected, the carrier invoice audit, the on-time delivery report, and the rate-shopping spreadsheet all run themselves on a schedule, with results landing in the systems where your ops, finance, and CX teams actually work.