Bloodhound is a Node.js package that allows you to retrieve tracking data from shipping carriers (DHL, FedEx, UPS, USPS) in a common format.
This module was inspired by the excellent
shipit module. We built Bloodhound to provide better support for parsing of timestamps (read more below).
Bloodhound interfaces with several carrier APIs and returns results in a single, unified format. Each carrier activity/movement/scan is represented as an event with a description, geographic location (city/state), and timestamp.
When it comes to timestamps there are two types of carrier APIs: those that include a UTC offset which can be easily parsed as proper dates, and those that provide timestamp strings that need to be interepreted based on the local timezone of the geographic location for the event.
When Bloodhound encounters a timestamp without a UTC offset if looks up the timezone by geocoding the event's geographic location. The returned results contain proper dates in the correct timezone.
Geocode results are cached in-memory locally. Geocode results can optionally be cached remotely in Redis.
Bloodhound can guess the carrier given a tracking number explicity through the
bloodhound.guessCarrier(trackingNumber) method. Bloodhound will also try to guess the carrier when tracking a package without specifying a carrier when using the
Bloodhound also examines each of the activity/movement/scan events for "shipped" and "delievered" event types (beyond simple electronic events like "shipping label created" or "manifest file sent"). When a matching event type is encountered Bloodhound returns a
const Bloodhound = ;const bloodhound =usps:userId: 'USPS_USER_ID';bloodhound;
Creates a new Bloodhound client. Each carrier requires a different combination of credentials (account numbers, meter numbers, passwords, user IDs, etc).
By default, when Bloodhound encounters a timestamp without a UTC offset it will geocode using OpenStreetMap (which does not require an API key). You can optionally use a different geocoder. You can also optionally cache geocode results in Redis.
const Bloodhound = ;const bloodhound =fedEx:account_number: '123456789'environment: 'live'key: 'abcdefghijklmnop'meter_number: '987654321'password: 'abcdefghijklmnopqrstuvwxy'geocoder:apiKey: 'GOOGLE_API_KEY'language: 'en'provider: 'google'region: '.us'pettyCache:host: '127.0.0.1'options:auth_pass: 'secret'port: 6379ups:accessKey: 'ABCDEFGHIJKLMNOPQ'password: 'password'username: 'username'usps:userId: 'USPS_USER_ID';bloodhound;
FedEx options are passed to the shipping-fedex module.
By default Bloodhound uses the OpenStreetMap geocode provider. You can optionally specify geocoder options which are passed to the node-geocode module.
By default Bloodhound caches geocode results in-memory locally. You can optionally enable caching of geocoder results to a remote Redis server. These options are passed to the petty-cache module.
The UPS API requires a username, password, and an access key.
The USPS API simply requires a user ID: https://www.usps.com/business/web-tools-apis/track-and-confirm-api.htm
Guesses the carrier of the specified tracking number.
const carrier = bloodhound;console;
bloodhound.track(trackingNumber, [carrier,] callback)
Retrieves tracking data for the specified tracking number.