Migrate from 2026-01 to 2026-07

The Base URL for the API has been updated. You must update the version in the URL path for all your API requests.

Version 2026-07 introduces the new Location resource and related endpoints:

  • POST /locations
  • GET /locations
  • GET /locations/{id}
  • PATCH /locations/{id}

This is a new optional resource. Existing integrations do not need to change unless they want to manage locations through Commerce API.

In 2026-01 and earlier, the location_id on order.pickup_location, fulfillment.pickup_location, and fulfillment.ship_from_location required the AfterShip internal warehouse UUID, which was not exposed by any Commerce API endpoint. From 2026-07, this field only accepts the public Location ID returned by the new Location Resource (§2 of Changelog).

Migration Steps

  1. Use GET /locations to obtain the public id for each location your integration references (or remember the id returned by POST /locations).
  2. Replace any hard-coded internal warehouse UUID values with the corresponding Location id.

Example

Before (2026-01):

preparing...

After (2026-07):

preparing...

For platform-sourced locations, use the composite Location id in the form app-<platform>-<app_key>-<external_id>.

If the supplied location_id does not match any Location under the organization, the endpoint returns 422 Unprocessable Entity with info: "The location does not exist." on the corresponding request_body.*.location_id path.

Migrate from legacy API to Versioned API

For all legacy API user (with the API URL https://api.aftership.com/commerce/v1), please visit 2024-04 migration guide for the detail instruction.