myspeedpost APImyspeedpost.com ↗
Track India Post Speed Post consignments via the myspeedpost.com API. Get current status, scan history, origin/destination, and delivery confirmation.
What is the myspeedpost API?
The myspeedpost.com API exposes a single track_shipment endpoint that returns up to 14 structured fields for any India Post Speed Post consignment number, including the full chronological scan-event history, origin and destination office details, article type, tariff, and a boolean delivery flag. It covers domestic Speed Post articles identified by the standard 13-character India Post consignment format.
curl -X GET 'https://api.parse.bot/scraper/61d60168-8624-44f0-a510-361e5475ae3d/track_shipment?tracking_number=EK123456789IN' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace myspeedpost-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: MySpeedPost SDK — track an India Post Speed Post consignment."""
from parse_apis.myspeedpost_com_api import MySpeedPost, TrackingNumberNotFound
client = MySpeedPost()
# Look up a shipment by its 13-character tracking number.
try:
shipment = client.shipments.get(tracking_number="EK123456789IN")
except TrackingNumberNotFound:
print("No booking information found for that tracking number.")
raise SystemExit
# Top-level shipment details
print(f"{shipment.tracking_number}: {shipment.current_status}")
print(f" Article type : {shipment.article_type}")
print(f" Tariff : {shipment.tariff}")
print(f" Delivered : {shipment.delivered}")
if shipment.delivered:
print(f" Delivered at : {shipment.delivered_at} — {shipment.delivery_location}")
# Origin and destination offices
print(f" From: {shipment.origin.office}, {shipment.origin.state}")
print(f" To : {shipment.destination.office}, {shipment.destination.city}")
# Walk the scan-event history (oldest first)
if shipment.events:
print(f"\n {shipment.event_count} scan events (showing first 3):")
for event in shipment.events[:3]:
print(f" {event.timestamp} {event.event} @ {event.office} ({event.pincode})")
print("\nexercised: shipments.get")
Returns the tracking record for one India Post Speed Post consignment: current status, article type and tariff, booking/last-update/delivery display dates, origin and destination office details, and the complete list of scan events sorted oldest to newest (each with an ISO-8601 UTC timestamp, event name and type code, office name and pincode, remarks, and, when the site resolves it, the next/forwarding office with its pincode, state and coordinates). One page fetch per call; the site refreshes its data from India Post on request, and last_synced_at says when. booked_on, last_updated and delivered_at are display strings as rendered by the site (e.g. one shape: '8 Aug 2026, 12:34 PM'); use events[*].timestamp for machine-readable times. Event fields that the site leaves blank are returned as null. A tracking number the site has no booking information for yields a stale_input (input_not_found) result; a malformed number yields stale_input (input_format_invalid) without contacting the site.
| Param | Type | Description |
|---|---|---|
| tracking_numberrequired | string | 13-character India Post consignment number: 2 letters, 9 digits, 2 letters (case-insensitive; normalized to upper case). |
{
"type": "object",
"fields": {
"events": "array of scan events oldest first: timestamp (ISO-8601 UTC), event, event_type, office, pincode, remarks (nullable), next_office, next_office_pincode, next_office_state, next_office_latitude, next_office_longitude (nullable)",
"origin": "object: office, pincode, state, country of booking (each nullable)",
"tariff": "postage display string with currency, e.g. '55.00 INR', null when not shown",
"booked_on": "booking date/time display string, null when not shown",
"delivered": "boolean, true when an ItemDelivered event exists",
"destination": "object: office, city, state, country of destination (each nullable)",
"event_count": "integer number of scan events",
"article_type": "service type string, null when not shown",
"delivered_at": "delivery date/time display string, null when not delivered",
"last_updated": "last status date/time display string, null when not shown",
"current_status": "latest status text (e.g. 'Item Delivered'), leading status emoji stripped",
"last_synced_at": "ISO-8601 UTC time the site last synced this consignment with India Post",
"tracking_number": "consignment number as shown by the site",
"tracking_status": "site sync status word, e.g. 'Completed'",
"delivery_location": "delivering office name, null when not delivered"
},
"sample": {
"data": {
"events": [
{
"event": "Item Booked",
"office": "Vookondi B.O",
"pincode": "508112",
"remarks": null,
"timestamp": "2026-08-08T07:04:04.000000Z",
"event_type": "ItemBooked",
"next_office": null,
"next_office_state": null,
"next_office_pincode": null,
"next_office_latitude": null,
"next_office_longitude": null
},
{
"event": "Item Delivered(Addressee)",
"office": "DC Shamirpet",
"pincode": "500078",
"remarks": "Delivered",
"timestamp": "2026-08-12T09:27:04.000000Z",
"event_type": "ItemDelivered",
"next_office": "DC Shamirpet",
"next_office_state": "Telangana",
"next_office_pincode": "500078",
"next_office_latitude": 17.5850938,
"next_office_longitude": 78.601083
}
],
"origin": {
"state": "Telangana",
"office": "Vookondi B.O",
"country": "INDIA",
"pincode": "508112"
},
"tariff": "55.00 INR",
"booked_on": "8 Aug 2026, 12:34 PM",
"delivered": true,
"destination": {
"city": "HYDERABAD",
"state": "TELANGANA",
"office": "Trimulgherry H.O",
"country": "INDIA"
},
"event_count": 26,
"article_type": "Inland Speed Post",
"delivered_at": "12 Aug 2026, 2:57 PM",
"last_updated": "12 Aug 2026, 2:57 PM",
"current_status": "Item Delivered",
"last_synced_at": "2026-09-22T14:39:47.000000Z",
"tracking_number": "EK123456789IN",
"tracking_status": "Completed",
"delivery_location": "Trimulgherry H.O"
},
"status": "success"
}
}About the myspeedpost API
What the API Returns
The track_shipment endpoint accepts one required parameter — tracking_number — which must be a 13-character India Post consignment number in the format AA999999999AA (case-insensitive). The response includes top-level fields for article_type, tariff (e.g. "55.00 INR"), booked_on, last_updated, and event_count, giving a quick summary of the article without parsing the event log.
Scan Event History
The events array contains every recorded scan event sorted oldest to newest. Each event object includes an ISO-8601 UTC timestamp, a human-readable event description, an event_type classifier, the handling office and its pincode, optional remarks, and a next_office field indicating where the article was routed. This makes it straightforward to reconstruct the full movement timeline or detect stalls between offices.
Origin, Destination, and Delivery
The origin object provides the booking office, pincode, state, and country. The destination object provides the destination office, city, state, and country. Each sub-field is nullable when not published by the source. The delivered boolean is true whenever an ItemDelivered event exists in the scan history, and delivered_at holds the corresponding delivery date/time display string when applicable.
The myspeedpost API is a managed, monitored endpoint for myspeedpost.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when myspeedpost.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official myspeedpost.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Notify e-commerce customers automatically when their Speed Post shipment is delivered by polling the
deliveredflag - Visualise the full transit path of a consignment by mapping each event's
officeandpincodein order - Detect delayed shipments by comparing
last_updatedagainst the current date and flagging gaps beyond a threshold - Audit last-mile delivery performance by extracting
ItemDeliveredevents and their timestamps across a batch of consignments - Build a customer-facing shipment tracker that displays
origin,destination, and theeventstimeline without requiring users to visit the India Post website - Cross-reference
tariffandarticle_typefields against booking records to verify correct postage was charged
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does India Post have an official developer API for Speed Post tracking?+
What does the `events` array actually contain, and how is it ordered?+
events represents one scan event recorded during the article's transit. Fields include timestamp (ISO-8601 UTC), event, event_type, office, pincode, remarks (nullable), and next_office. Events are sorted oldest to newest, so the first element is the booking scan and the last is the most recent update.Can I track non-Speed Post India Post products such as Registered Post, Parcel Post, or EMS?+
Are all response fields always populated?+
tariff, booked_on, last_updated, delivered_at, article_type, and the sub-fields within origin and destination are explicitly nullable. They return null when the source does not publish that value for the consignment in question. Always handle null values in your integration.Does the API support bulk or batch tracking of multiple consignments in one request?+
track_shipment endpoint accepts a single tracking_number per request. For multiple consignments, you would call the endpoint once per number. You can fork this API on Parse and revise it to add a batch endpoint that accepts an array of tracking numbers.