Reference · built on requestConnectorShipping & logistics

EasyPost

Multi-carrier shipments, rates, trackers, webhook events, address verification, and pickups from the EasyPost API.

Request accessPricing ↗

About

EasyPost is a multi-carrier shipping API. A Shipment carries a to and from Address and a Parcel; creating one populates Rate objects from your CarrierAccounts, and buying a rate returns a postage_label and tracking_code. A Tracker follows any tracking code, and Webhooks deliver Event objects such as tracker.updated to your endpoint. Every account gets a USPS account managed by EasyPost; you add your own UPS, FedEx, DHL Express, Canada Post, or Royal Mail credentials as CarrierAccounts.

Fibric reads trackers and events across all of them, so one operator can watch every carrier you ship with and propose the customer notice, refund, or pickup from the same feed.

This is a reference listing. It documents what Fibric would read from EasyPost and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Tracker status (pre_transit, in_transit, out_for_delivery, delivered), status_detail, est_delivery_date, signed_by, and tracking_details scan history
  • Event objects pushed to your Webhook: tracker.created, tracker.updated, batch.updated, scan_form.created, refund.successful, and others
  • Rate objects per carrier and service on each Shipment, with carrier, service, price, and delivery estimate
  • Address verifications (delivery and zip4) with the residential flag set on US addresses
  • PickupRate options for a Pickup across compatible carrier accounts
  • CarrierAccounts on file and the credential fields each CarrierType requires

Proposed actions

  • Target capability: propose buying a Rate on a Shipment (POST /shipments/:id/buy) and hand back the label in PNG, PDF, ZPL, or EPL2
  • Target capability: propose a refund for a purchased label through the Shipment refund endpoint
  • Target capability: propose a Tracker for a code bought outside EasyPost through POST /trackers
  • Target capability: propose scheduling a Pickup (POST /pickups, then /buy) or cancelling one before it completes
  • Target capability: propose a Webhook registration with a webhook_secret so events arrive HMAC-signed

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • One exception feed for every carrier

    Consume tracker.updated events across USPS, UPS, FedEx, and DHL Express. When status_detail reads delayed or address_correction, propose the customer notice and the order note.

    With Carrier Exception, Tracking Sync

  • Pick the ship-from location by rate and date

    Create a Shipment from each candidate warehouse, compare the Rate objects, and propose the purchase that meets the promise date at the lowest price.

    With Ship-From Routing

  • Repair the address before buying the label

    Create the to_address with verify set, read the delivery and zip4 results, and propose the corrected fields for approval before any rate is bought.

    With Address Repair

Requirements

  • An EasyPost account with Test and Production API keys from the Dashboard
  • CarrierAccount objects with your own credentials for carriers beyond the EasyPost-managed USPS account
  • A public HTTPS endpoint that returns a 2XX status for each Event
  • Address, Parcel, and, for international, CustomsInfo on every Shipment
Authentication
An API key used as the Basic Authentication username with no password, over TLS 1.2; Test keys for trial requests, Production keys for labels that are billed.

Limits

  • Shipment, Address, and Pickup objects are immutable once created; a change means a new object
  • Webhook endpoints that repeatedly fail may be disabled automatically and must be re-enabled
  • A Tracker with the same tracking code and carrier created within three months returns the original
  • Some carriers need a custom_workflow through the EasyPost UI rather than credentials submitted by API

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request EasyPost ↗

Questions and answers

Which events can EasyPost send to a webhook?
Tracker (tracker.created, tracker.updated), Batch, ScanForm, Refund (refund.successful), Insurance, Claims, Payment, Report, and Shipment Invoice events. Each arrives as an Event with result, previous_attributes, and mode. Set a webhook_secret and EasyPost signs each event in the X-Hmac-Signature header.
Do I need my own carrier accounts?
Not for USPS: each EasyPost account includes a USPS account managed by EasyPost. For UPS, FedEx, DHL Express, Canada Post, Royal Mail, and others, create CarrierAccount objects with your own credentials using a Production API key.
What label formats are returned?
PNG by default. GET /shipments/:id/label converts to PDF, ZPL, or EPL2. EasyPost notes that conversion works best for 4x6 labels converted from PNG to ZPL.
Ask about EasyPost

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with EasyPost through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy