1. Summary

To improve performance and scalability of our platform, Innoship is separating read-oriented (query) operations from the main API. A defined set of endpoints currently served by api.innoship.com is being moved to a new dedicated host: query.innoship.com.

Only the base URL (host) changes. Routes, path parameters, query parameters, request and response formats, and authentication remain the same.

2. Affected endpoints

All the 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) 

Order service 

GET 

/api/Order/by-location/{externalLocationId}/{from}/{to} 

Track service 

POST 

/api/Track/by-awb/with-return 

POST 

/api/Track/by-external-order-id 

POST 

/api/Track/return/by-awb 

Location service 

GET 

/api/Location/Countries 

GET 

/api/Location/Counties/{countryCode} 

GET 

/api/Location/Localities/{countyId} 

GET 

/api/Location/Postalcodes/{localityId} 

GET 

/api/Location/Postalcodes/Country/{countryCode} 

GET 

/api/Location/Postalcodes/{countryCode}/{postalCode} 

GET 

/api/Location/ClientLocations 

GET 

/api/Location/FixedLocations 

GET 

/api/Location/FixedLocationsWithErrors 

GET 

/api/Location/FixedLocation/{id} 

Courier service 

GET 

/api/Courier/All 

Feedback service 

GET 

/api/Feedback/{from}/{to} 


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. What you need to do

  • Update the base URL from https://api.innoship.com to https://query.innoship.com for the 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.

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.

  • 30.06.2027 — the affected endpoints are retired from api.innoship.com and will return an error. All traffic must use query.innoship.com from this date.

5. Example

Before:

GET https://api.innoship.com/api/Order/by-location/1024/2026-07-01/2026-07-15

After:

GET https://query.innoship.com/api/Order/by-location/1024/2026-07-01/2026-07-15

6. Support

If you have questions or need assistance with migration, 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.