Changelog

This page contains the changelog of the current API version. For the past changelog, please refer to this page.

2026-01 (2026-01-08)

1. General

CHANGE	BEFORE	AFTER
Base URL	https://api.aftership.com/commerce/2025-07	https://api.aftership.com/commerce/2026-01

2. Fulfillment Resource Changes

2.1 Removed ship action endpoint

The endpoint POST /fulfillments/{id}/ship has been removed to streamline the API. You should now use the general update endpoint to update fulfillment status and trackings.

Affected Endpoints

• POST /fulfillments/{id}/ship (Removed)

Migration Guide

Instead of calling the specific ship endpoint, send a PATCH request with the updated status:

preparing...

2.2 Updated trackings structure

The trackings object within the fulfillment resource has been updated to support better integration with the Tracking API. It now supports two mutually exclusive modes:

1. Reference Mode: Pass the tracking ID which created via the Tracking API. (Recommended for full tracking features).
2. Inline Mode: Provide a tracking_number (and optional slug) for simple record-keeping. This is strictly for record-keeping purposes and does not create an active tracking task, and hence AfterShip system would not provide status updates to this tracking number.

Affected Endpoints (Request And Response Body)

• POST /fulfillments
• PATCH /fulfillments/{id}

Affected Endpoints (Response Body)

• GET /fulfillments
• GET /fulfillments/{id}
• POST /fulfillments/{id}/update-status

Request Example

Option 1: Reference Mode (Link existing tracking) Use this when you have already created a tracking resource via the Tracking API.

preparing...

Option 2: Inline Mode (for record-keeping purpose only) Use this when you only need to record the tracking number without active tracking status updates.

preparing...

Note: You cannot provide both id and tracking_number in the same tracking object.