1. Summary
To improve performance and scalability of our platform, Innoship is separating read-oriented (query) operations from the main API. The Track service endpoints currently served by api.innoship.com are being moved to a new dedicated host: query.innoship.com.
You have two ways to adapt: migrate your Track calls to the new host, or implement the Track push method and stop querying the Track endpoints altogether. Both options are described in section 3.
If you choose to migrate, only the base URL (host) changes. Routes, path parameters, query parameters, request and response formats, and authentication remain the same.
2. Affected endpoints
The Track operations listed below move from api.innoship.com to query.innoship.com. The paths themselves do not change.
Method | Endpoint path (unchanged — only the host changes) |
Track service | |
POST | /api/Track/by-awb/with-return |
POST | /api/Track/by-external-order-id |
POST | /api/Track/return/by-awb |
All other endpoints — including order creation, order updates, cancellations, pickup requests, labels, pricing, manifests, and any endpoint not listed above — remain on api.innoship.com and are not affected by this change.
3. Your options
You can choose either of the options below, for your entire integration or per system. Whichever you choose, it must be in place before the retirement date in section 4.
Option A — Migrate to the new host
Update the base URL from https://api.innoship.com to https://query.innoship.com for the Track endpoints listed in section 2 only.
Keep your existing API key / authentication headers unchanged — the same credentials are valid on both hosts.
If your infrastructure uses an allow-list (firewall, proxy, egress rules), add query.innoship.com to it.
Test your integration against the new host before the deadline in section 4.
No changes are required to request bodies, response parsing, or error handling.
Option B — Replace Track queries with Track push
With Track push, Innoship POSTs order status updates to an endpoint you expose, as a JSON array of objects, whenever a status changes — no polling of the Track endpoints is needed.
The object pushed is the same as the one returned by the Track service, so your existing response parsing can be reused.
If you already use Track push for some of your systems or countries, the same implementation can be extended to the rest of your integration.
Your endpoint may use any authentication method.
Once Track push is active, the affected Track endpoints no longer need to be called and no host migration is required.
The full Track push specification, including an example POST body, is available at: https://support.innoship.com/support/solutions/articles/80001025726-track-push
4. Timeline
20.07.2026 — query.innoship.com is live and available for testing. Both hosts serve the affected endpoints in parallel.
31.03.2027 — recommended date by which all clients complete the migration or have Track push active.
30.06.2027 — the affected endpoints are retired from api.innoship.com and will return an error. From this date, Track data is available only via query.innoship.com or Track push.
5. Example
Before:
POST https://api.innoship.com/api/Track/by-awb/with-return
After (Option A):
POST https://query.innoship.com/api/Track/by-awb/with-return
With Option B, no call is made — Innoship pushes the same tracking object to your endpoint as statuses change.
6. Support
If you have questions or need assistance with the migration or with enabling Track push, please contact our support team support@innoship.com or through your account manager. We are happy to help you validate your integration against the new host or activate Track push where needed.