Supply the request parameters in the body #54
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In order to comply with the upcoming change in the bol API, the parameters are now supplied in the body instead of the URL.
|
Thanks for the effort @wgriffioen. It did not work, I had to test a lot more for all the right flows, but in #55 I have a working version of this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As noted in the Retailer API documentation, the request parameters required to obtain a token must be included in the request body rather than in the URL parameters. While bol.com has previously accepted parameters in the URL, this approach will no longer work starting November 18th this year.
To ensure compatibility with this upcoming change in the Bol API, the parameters are now included in the request body instead of the URL.