You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is reflected in the API and the Ecwid UI. Previously, the Order IDs had the ‘number’ field type (e.g.167729309). From now on, the new fields (‘id’, ‘orderId’) with the ‘string’ type will be used instead of the old fields (‘orderNumber’, ‘vendorNumber’ and ‘id’ in Webhook events). This requires appropriate changes in your applications.
Webhooks, /orders endpoint have been changed
New id field instead of orderNumber and vendorOrderNumber fields in Ecwid REST API’s GET/PUT/DELETE /orders endpoint;
New orderId field in the response to the ‘Create order (POST)’ request;
New orderId field in Webhook events;
Old vendorOrderNumber and orderNumber are deprecated from now on.
Steps to make sure your up to date with the changes
Change order ID display in your applications.
Use new field from webhook to get order details.
Use the new order “id” field for Ecwid REST API PUT/DELETE requests.
Use the new order “id” field for order reference in payment applications.
The text was updated successfully, but these errors were encountered:
[ from ecwid developers mail list 11/11/2020 ]
Order IDs now have the string type
This is reflected in the API and the Ecwid UI. Previously, the Order IDs had the ‘number’ field type (e.g.167729309). From now on, the new fields (‘id’, ‘orderId’) with the ‘string’ type will be used instead of the old fields (‘orderNumber’, ‘vendorNumber’ and ‘id’ in Webhook events). This requires appropriate changes in your applications.
Webhooks, /orders endpoint have been changed
Steps to make sure your up to date with the changes
The text was updated successfully, but these errors were encountered: