The Offer API is used to manage offers. An offer always needs a product as a base to which the offer refers. The product is not merchant-specific (because it describes a product in general), but the offer is. The offer describes the details at which a merchant wants to offer a product on a specific channel.
For the product "Coca Cola, glass bottle, 0.4L", a merchant creates the offer "6-pack, 10 pieces available in stock, each at a price of 4.00 US dollars with a delivery time of 2-4 days". This and similar offer data are managed by the Offer API.
The current API version is: 1.0.2
We use a variety of state-of-the-art techniques to ensure that our code meets the highest quality criteria. Some examples are:
- SOLID principle
- Clean as you code:tm: approach
- 4-eyes approval on QC
- Semiautomated Unit-, Integration- and End2End-tests
- positive tests / negative tests / destructive tests in aware of false positive results / false negative results
- Sonarcloud
Read more about our code quality approach in our wiki: Code Quality.
💡 If you still notice something bad, we are happy to have a strong community to solve the problem together with you: How to provide feedback
Generally, bugs and feature requests for the API or docs should be Github issue. Everything else should be discussed here: Discussions.
Note that by submitting your feedback, we have the right to use it.1
Footnotes
-
Legalese-wise, this means it’s considered non-confidential and non-proprietary to you, and you grant Qilin.Cloud a non-exclusive, worldwide, royalty-free, irrevocable, sub-licensable, perpetual license to use and publish those ideas and materials for any purpose, without compensation to you. ↩