tracker.shadowfax.in APItracker.shadowfax.in ↗
Track Shadowfax shipments by AWB number, validate tracking IDs, and fetch blog posts and header announcements via the Shadowfax Tracker API.
curl -X GET 'https://api.parse.bot/scraper/e0c1a6cc-cef2-4ffe-95f5-4ace8bd7b83f/validate_tracking_id?awb_number=SF99887766XX' \ -H 'X-API-Key: $PARSE_API_KEY'
Validate whether a given AWB number is a valid Shadowfax shipment ID. Returns valid=true with the unique_code if the AWB exists, or valid=false with an error message if not.
| Param | Type | Description |
|---|---|---|
| awb_numberrequired | string | Shipment AWB/Tracking ID to validate. |
{
"type": "object",
"fields": {
"valid": "boolean indicating whether the AWB number is valid",
"message": "string with validation result message",
"unique_code": "string unique code for the shipment (present when valid is true, null otherwise)"
},
"sample": {
"data": {
"valid": false,
"message": "Invalid AWB Number"
},
"status": "success"
}
}About the tracker.shadowfax.in API
The Shadowfax Tracker API exposes 4 endpoints covering shipment validation, live tracking status, blog content, and website header announcements. The track_shipment endpoint accepts an AWB number and returns the current delivery status alongside a unique shipment code. The validate_tracking_id endpoint lets you confirm whether an AWB belongs to a real Shadowfax shipment before committing it to a workflow.
Shipment Tracking and Validation
The two core tracking endpoints — validate_tracking_id and track_shipment — both accept a single required parameter, awb_number. validate_tracking_id returns a valid boolean, a message string, and a unique_code when the AWB exists. track_shipment returns the same valid flag plus a status string and the unique_code. When an AWB is invalid, both endpoints set valid to false, return an error message, and null out unique_code and status. This two-step pattern is useful when you want to gate downstream processing on confirmed AWB existence before fetching full status.
Blog and Content Endpoints
get_blogs returns a paginated list of Shadowfax blog posts. Each item in the data array includes _id, title, slug, image, publishedBy, category, content, date, metaTitle, and metaDescription. The response also exposes total (the full count of available posts) and nextPage for pagination. This makes it straightforward to build a full content feed or mirror the blog index.
Header Configuration
get_header_config returns the current active header announcements from the Shadowfax website. The data array contains announcement objects when banners are live, and is empty when none are configured. The error boolean is present on both content endpoints to flag retrieval failures cleanly.
- Validate a batch of customer-submitted AWB numbers before ingesting them into an order management system using
validate_tracking_id. - Poll
track_shipmenton a schedule to push delivery status updates to customers via SMS or email. - Aggregate Shadowfax blog content into an internal knowledge base using the
slug,category, andcontentfields fromget_blogs. - Display active Shadowfax service announcements in a logistics dashboard by reading
get_header_config. - Build a shipment validity pre-check in a returns portal to reject unrecognized AWB numbers before processing refunds.
- Sync blog publication dates and
metaTitlefields to an SEO monitoring tool tracking Shadowfax content updates.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Shadowfax have an official public developer API?+
What does `track_shipment` return for an invalid AWB number?+
track_shipment returns valid: false, a descriptive message string, and null values for both status and unique_code. The same valid flag and message pattern applies to validate_tracking_id, so you can handle errors uniformly across both endpoints.Does `get_blogs` support filtering by category or date?+
nextPage field to step through results. The response objects do include category and date fields, so client-side filtering is possible. You can fork this API on Parse and revise it to add server-side category or date filtering.Does the API expose detailed shipment events or delivery timestamps beyond the current status?+
track_shipment returns a single status string and unique_code rather than a full event timeline or timestamp history. You can fork this API on Parse and revise it to add an endpoint that surfaces per-event delivery history if that data becomes accessible.How does pagination work in `get_blogs`?+
total integer (total posts available) and a nextPage integer pointing to the next page. Iterate using nextPage until all posts are retrieved. There are no inputs on the current endpoint to specify a page number directly.