Stay updated with the latest improvements, bug fixes, and new features.
GET /invoices
– Returns a paginated list of invoices. Introduced in this version to support invoice visibility and filtering.GET /invoices/{invoiceId}/transactions
– Fetches transaction-level detail for a given invoice.GET /transaction-fees
– Lists available transaction fee types within the billing system.POST /transactions:query
– Enables advanced querying of transactions with support for filters and pagination.GET /product/{productId}/variants
POST /product/{productId}/variants
PATCH /product/{productId}/variants
– New set of endpoints for managing product variants in bulk.
POST /product:moveVariants
– Allows moving multiple variants to a different product in one operation.
POST /product/{productId}:moveVariants
– Enables merging variants into an existing product.
POST /variant/{variantId}:convertToBundle
– Converts a standard variant into a bundled product.
POST /variant/{variantId}:merge
– Combines multiple variants into a single entity.
DELETE /product/{productId}
– Deletes a product by ID. This method is now officially supported.
POST /receiving:setExternalSync
– New operation to toggle the externalSync
flag on receiving orders.GET /return/{id}/statushistory
– This endpoint has been deprecated and is no longer available in the latest version./
) to colon-style actions (:action
) or applying hyphenated names.Old Path (v2.0) | New Path (2025-07) |
---|---|
/order/estimate | /order:estimate |
/order/{orderId}/cancel | /order/{orderId}:cancel |
/order/{orderId}/shipment/{shipmentId}/cancel | /order/{orderId}/shipment/{shipmentId}:cancel |
/order/{orderId}/storeOrderJson | /order/{orderId}/store-order-json |
/shippingmethod | /shipping-method |
/shipment/:bulkUpdateTrackingUpload | /shipment:batchUpdateTrackingUpload |
/shipment/cancelbulk | /shipment:batchCancel |
/shipment/{shipmentId}/cancel | /shipment/{shipmentId}:cancel |
/receiving/{id}/cancel | /receiving/{id}:cancel |
/fulfillmentCenter | /fulfillment-center |
/return/{id}/cancel | /return/{id}:cancel |
PUT 1.0/shipment
endpoint to indicate when tracking information has been uploaded. Use this endpoint to acknowledge that tracking details have been successfully synced to your system. Here is example use case:GET 1.0/order?HasTracking=true&IsTrackingUploaded=false
to retrieve orders where tracking has been provided but not yet confirmed as uploaded.PUT 1.0/shipment
endpoint to mark it as uploaded.GET 2.0/simulate/status/{simulation_id}
endpoint in the Sandbox Environment to fetch the status of a registered simulation.POST 2.0/simulate/shipment
endpoint in the Sandbox Environment to request simulation for processing a shipment to ‘Shipped’ and ‘Delivered’ statuses.GET 2.0/receiving
endpoint to request multiple Warehouse Receiving Orders (WROs), supporting various query parameters like fulfillment center ID and WRO insert date.1.0/receiving
endpoints. Users are encouraged to migrate to 2.0/receiving
. Note: The models returned by 2.0/receiving
will no longer contain box info; this will be moved to a separate endpoint before /receiving
is removed permanently.purchase_order_number
attribute to the Receiving API’s request and response structures.total_sellable_quantity
attribute to Inventory API endpoints, calculated by subtracting the total exception quantity from the fulfillable quantity.reference_id
.referenceId
field as a filter to the ‘Get Orders’ endpoint.packaging_attribute
field to Inventory API endpoints.Next-Page
headers returned by endpoints with multiple pages.