We designed the APIs in a way that they are instantly applicable to your front-end use cases, meaning that you don't necessarily need to implement the back-end integration to be able to use this service. Simply log user activities, and this alone will let you receive behavior-based recommendations (i.e. Top selling, Trending, Featured, Related).
\nThe API endpoint is located here https://wiser.expertvillagemedia.com/api/partner . All API requests should use the above URL as their base url.Shop name (e.g. myshop.myshopify.com) Partner Name and secret key are required parameters for each API. Calls made over plain HTTP will fail. API requests without authentication will also fail.Responses from the Wiser API are returned in JSON format unless otherwise stipulated.You need pass parameters as GET method.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"24381428","collectionId":"3f426b8f-2a48-449d-b78c-f0bdf215769f","publishedId":"2s9YkgC4uv","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2023-12-07T17:00:26.000Z"},"item":[{"name":"Wiser Order Note Attributes – Integration Guide","item":[],"id":"46e82fc0-7fa4-43f1-ac37-5867e78d10fe","description":"When a product is added to the cart using Wiser widgets (via API), we need to store specific details in order note attributes. This helps in tracking product recommendations and sales attribution.
\nRequired Attributes
\n1. wiserai_productID
Stores all product IDs added via Wiser.
If multiple products are added, store them as comma-separated values.
\n\nExample:
\n
wiserai_productID: 7856563748945,7770397704273
2. wiserai_type
Indicates the source of the API request.
\nPossible Values:
\nmobile_api
desktop_api
\n\nExample:
\n
wiserai_type: mobile_api
3. wiserai_Page
Stores page source from where the product was added
If multiple products → use comma-separated values
Allowed values
\n\n\nExample:
\n
wiserai_Page: index,product,collection,cart,myaccount,other,404,search,wiser_checkout,wiser_thankyou,wiser_orderstatus
4. wiserai_widget
Stores widget names from which product was added
\nSupports only predefined widget names. If multiple → use comma-separated values
\n\n\nExample:
\n
wiserai_widget: alsobought,recently_products,recently_related_products,related_products,top_selling,trending_products,new_arrival,featured_collections,recommended_products
Special Case (Very Important)
\nFor these pages:
\nwiser_checkout
wiser_thankyou
wiser_orderstatus
👉 Format will be different
\nFormat: {page} = {widget_name}__{productId}
\n\n\nExamples
\n
✔ Special Pages (Checkout / Thankyou / Order Status)
wiser_checkout: new_arrival__{productId}
wiser_thankyou: new_arrival__{productId}
wiser_orderstatus: new_arrival__{productId},{productId}
When to Set These Attributes
\nAt the time of Add to Cart (API call)
\nEnsure attributes are attached before checkout so they are available in the order
\nImplementation Logic
\nDetect product added via Wiser widget/API.
\nCapture the product ID(s).
\nIdentify platform type:
\nMobile → mobile_api
Desktop → desktop_api
Attach both attributes to cart/order notes.
\nAfter API call, the cart should contain attributes like this:
\n{
\"token\": \"abc123\",
\"items\": [
{
\"id\": 7856563748945,
\"quantity\": 1
}
],
\"attributes\": {
\"wiserai_productID\": \"7856563748945,7770397704273\",
\"wiserai_type\": \"mobile_api\",
\"wiserai_Page\": \"index,index\",
\"wiserai_widget\": \"new_arrival,top_selling\"
}
}