Changelog
This page contains the changelog of the current API version. For the past changelog, please refer to this page.
2025-07 (2025-07-10)
1. General
| CHANGE | BEFORE | AFTER |
|---|---|---|
| Base URL | https://api.aftership.com/commerce/2025-04 | https://api.aftership.com/commerce/2025-07 |
2. Fulfillment Resource Changes
2.1 New ship_from_location.address field
ship_from_location.address fieldWhen creating a fulfillment, the ship_from_location field has been enhanced. You can now specify the shipping origin by providing either an existing location_id or a new address object directly. You must provide one of these fields, but it is not permitted to provide both simultaneously.
Affected Endpoints (Request Body)
POST /fulfillments
Request Example
You can now provide an address object for ship_from_location:
preparing...
The response body for this endpoint remains unchanged.
2.2 Removed ship_to_location field
The ship_to_location field has been deprecated and completely removed from the Fulfillment resource. (Note: This field is not shipping_address. It was originally designed for the BOSS scenario under BOPIS. Since alternative methods will be introduced in the future to support this scenario, this field is being deprecated.)
This change affects both the request and response for creating a fulfillment, and only the response body for all other fulfillment-related endpoints.
Affected Endpoints (Request and Response Body)
- POST /fulfillments
- PATCH /fulfillments/{id}
Affected Endpoints (Response Body only)
- GET /fulfillments
- GET /fulfillments/{id}
- POST /fulfillments/{id}/update-status
- POST /fulfillments/{id}/ship