Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

It’s recommended, to go over existing production sheets in the platform and confirm that the correct type is assigned.

Appendix A - Orders endpoint changes

If you need them unchanged for your API integration, you can use the legacy endpoints, which will return all the old fields:

  • GET api/v2.0/service-panel/services/<service_id>/orders/legacy/

  • GET api/v2.0/user-panel/orders/legacy/

The following 2 GET endpoints of our API have been changed:

  • GET api/v2.0/service-panel/services/<service_id>/orders/

  • GET api/v2.0/user-panel/orders/

The customer field is not removed, it will stay in the response.

Here is the list of the changes:

The following fields are removed

  • currency

  • feesPrice

  • isCreatedBySharedUser

  • minPrice

  • minPriceDiff

  • taxRate

  • payment.paymentAttachments

  • status.defaultNextStatus

The following fields are changed

  • partner - only keep the fields name and id of partner, remove all other fields

  • shippingMethod - only keep the fields name and id of shippingMethod, remove all other fields

The following fields remain unchanged:

  • customer

  • billingAddress

  • createdAt

  • createdBy

  • deliveryDaysMax

  • deliveryDaysMin

  • deliveryInstructions

  • fullNumber

  • id

  • products

  • number

  • numberOfComments 0,

  • numberOfLines 1,

  • payment

  • partner

  • pickupLocation

  • projectId

  • referenceNumber

  • salesTransactionType

  • sequenceNumber

  • subtotalPrice

  • technologies

  • title

  • shippingAddress

  • shippingMethod

  • status

  • totalPrice

  • totalItemsQuantity