Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to V6.4 API #5

Open
harm-smits opened this issue Oct 4, 2021 · 7 comments
Open

Update to V6.4 API #5

harm-smits opened this issue Oct 4, 2021 · 7 comments

Comments

@harm-smits
Copy link
Collaborator

harm-smits commented Oct 4, 2021

Requires the following endpoints to be added:

Retailer promotions

  • /retailer/promotions
  • /retailer/promotions/{promotion-id}

Request an unpublished offer report containing all unpublished offers and reasons.

  • /retailer/offers/unpublished
  • /retailer/offers/unpublished/{report-id}

There are also a number of model changes (+ addition, ~ changed, - removed):

+ Asset (url, labels)
+ BestSellingOffer (countryCode, unitPrice)
+ Campaign (name, startDateTime, endDateTime)
~ CustomerDetails
~ DeliveryOption
~ Inventory
~ LabelPrice
~ PackageRestrictions
+ Product (ean, relevanceScores, maximumPrice, bestSellingOffers)
~ ProductContent (+assets)
+ Promotion (promotionId, title, startDateTime, endDateTime, countries, promotionType, products, retailerSpecificPromotion)
+ Promotions (promotions)
+ ReducedProduct (ean)
+ ReducedPromotion (promotionId, title, startDateTime, endDateTime, countries, promotionType, retailerSpecificPromotion)
~ ReducedShipment
~ ReducedTransport
~ Reduction
+ RelevanceScore (countryCode, relevanceScore)
~ Shipment
+ TransportEvent (eventCode, eventDateTime)

Breaking changes

CustomerDetails

~ Salutation has been changed to salutation from salutationCode for custom salutations. It is also no longer bound by an enumerable.
~ houseNumberExtended has been renamed to houseNumberExtension

DeliveryOption

~ First only labelPrice and packageRestrictions were required, now a lot more attrbiutes are required. Namely labelDisplayName, labelPrice, labelType, packageRestrictions, recommended, shippingLabelOfferId and transporterCode
+ recommended
+ labelDisplayName

Inventory

- bsku has been removed and is no longer a required attribute.

LabelPrice

+ totalPrice is now required

PackageRestrictions

+ maxDimensions and maxWeight are now required attributes.

ReducedShipment

~ shipmentId is now a string instead of an int64.

ReducedTransport

~ transportId is now a string instead of an int64.

Reduction

~ endDate is no longer required

Shipment

~ shipmentId is now a string instead of an int64.

ShipmentTransport

~ transportId is now a string instead of an int64.
+ transportEvents has been added

A few notable changes:

  1. The enum for countries has disappeared. Most likely bol.com will want to expand to e.g. germany, hence these restrictions are removed.
  2. Salutation is no longer an enum. Customers might be able to specify a custom salutation in the future.
  3. The product content API now allows assets to be attached.
  4. TransportEvents allow you to view the package status from labels from bol.com
@WeTurkstra
Copy link

Thanks for all the work you are doing on this library.
When is v6 going to be supported?

Is there anything i can do to help you to support the next version?

@harm-smits
Copy link
Collaborator Author

This was scheduled for a few weeks from now as the release for v7 is also approaching.

@harm-smits
Copy link
Collaborator Author

@WeTurkstra For now, this has been archived. We have migrated all Customers to a third party integrator which has a single API for all marketplaces. You can attempt to generate a new SDK by downloading the swagger files and generating a PHP client though :)

@WeTurkstra
Copy link

@harm-smits Thanks for your message. Too bad this library has been discontinued. Thanks for all the work you have done for it!
I will try it.

@vanengers
Copy link

Are you saying this library is unusable when V5 is deprecated?

@WeTurkstra
Copy link

Unfortunatly that seems to be the case :(

@harm-smits
Copy link
Collaborator Author

@vanengers Yes. But, as mentioned before, you can generate an entire SDK with swagger these days, so I don't really see much use in regenerating an up to date SDK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants