Introduction
Quote, book and track shipments across Indonesian couriers with one API.
- Product
- APIShipping Engine API
- Section
- Get started
- Reading time
- 2 min read
The Shipping Engine API lets your system work with more than a dozen Indonesian couriers through one integration. Couriers include JNE, J&T, SPX and Ninja Xpress, and instant couriers such as Lalamove and Grab. You send one request format, and Shipping Engine handles each courier's quirks, normalises their statuses, and bills everything from one balance.
Looking for something else?
Use Fastrac App to send parcels without code, or Fastrac Shop to run an online store.
How an integration fits together
Every shipment goes through the same four steps:
- 1subdistrictId
YouShipping Engine
Find the region
Turn each address into the ID of its subdistrict.
GET/b2b/region/find
- 2shippingRateCode
YouShipping Engine
Get rates
Describe the parcel and route. Get a price from every courier.
POST/b2b/shipping-rate
- 3airwayBill
YouShipping Engine
Create the order
Book the rate your customer picked. The courier is booked for you.
POST/b2b/orders
- 4
Shipping EngineYou
Track
Shipping Engine calls your webhook each time the status changes.
EVENTshipment.* webhooks
→ status
- Find regions. Indonesian addresses are matched to a subdistrict (kelurahan/desa). You look up its ID once per address.
- Get rates. You describe the parcel and route, and Shipping Engine returns a priced quote for each courier service that can carry it.
- Create an order. You book the quote the customer picked. Shipping Engine deducts the price from your balance and books the courier.
- Track. Shipping Engine sends a webhook every time the shipment changes status.
Not a developer?
If you use the Fastrac dashboard or app to send parcels, run a Fastrac Shop, or manage your balance, see the Fastrac App or Fastrac Shop docs.
Start here
Quickstart
Ship your first order in the sandbox in about 10 minutes.
Plan your integration
Pick the features you need and the decisions to make up front.
Order and shipment lifecycle
Every status a shipment goes through, and what to do at each.
Webhooks
Get notified the moment a shipment changes status.
Guides
Book, track, cancel, COD, multi-stop and more, step by step.
API reference
Every endpoint and field, with a request playground.
Conventions used across the API
| Topic | Convention |
|---|---|
| Format | JSON over HTTPS. Send Content-Type: application/json. |
| Authentication | Authorization: Bearer <access_token>, from the OAuth2 client-credentials flow. See Quickstart. |
| Success responses | Wrapped in { "statusCode", "message", "data" }. Your payload is always in data. |
| Errors | { "statusCode", "message", "error" }. message is a list when several fields fail validation. See Errors. |
| Money | Whole Rupiah as integers, for example 12984 means Rp 12.984. |
| Weight and size | Weight in grams, dimensions in centimetres. |
| Time | ISO 8601. Send an offset, for example 2026-11-21T10:00:00+07:00. Times without an offset are read as WIB. |
| Environments | Sandbox for building and testing, production for real shipments. Same client_id, different secret and host. |
Was this page helpful?