In my previous blog posts, I introduced our data models for product types, designs, products and articles to you and told you how to retrieve those data from our data API. In this blog post, I will tell you, how you can retrieve the corresponding images for that data from the image API, in order to display product type, design or product images in your custom applications.
Understanding the Different Image Types
Our image API delivers in general images for product types, designs, products, product type appearances, print colors and fonts.
Product Type Images
For product types, we deliver the following images:
Today, we released a fix for the recent search issues with marketplace and confomat search and search indexing on eu and na platform. The major changes are as follows:
- Faster Index Updates: We fixed the problem that changes on marketplace articles or designs took sometimes hours to be reflected in the actual search result, e.g. adding or removing a tag. Changes on articles or designs should now be reflected in the search result in at most 10 minutes (mostly because of caching and replication issues).
- Search Terms AND Connected: All search terms are AND connected in marketplace and Confomat search now when conducting a search – they were OR connected before. AND connected means, that all terms must occur in an article or design. Thus, we have much better results when customers enter more than one search term, for example “weißes männer shirt sterne herz deutschland” on the german marketplace or “sterne deutschland herz” in the confomat search. In case no article matches the AND connected search terms, the rule is that for more than 2 terms 2 terms must match and the additional ones are optional.
- Search Supports Phrase Search and Exclusion: The fixed search core supports phrase search, e.g. “I heart berlin”, as well as exclusions, e.g. “weltmeister deutschland -brasilien”, now. However, this needs to be enabled in marketplace search on PHP side and in design search in Confomat first. Continue reading “Platform Search Fix Released Today”
In one of my last blog posts, I told you about our product model and described what the difference between article and product is. I also told you how to retrieve products and articles and gave you a first idea on how to create new products.
In this blog post, I will tell you more about our basket model and how you can use baskets to add articles or products as basket items and forward customers with these baskets to our HTML checkout.
Understanding the Basket Model
In our terminology, a basket contains a set of abstract basket items that link concrete basket item elements. Right now, two concrete basket item elements are supported: Spreadshirt product and article. However, the mechanism is extendable and will later allow to support articles from external partner as well.
A typical basket, e.g. a basket with one article, is illustrated in the picture above. A basket has right now the following characteristics:
- Core Data: Each basket can have a token, a shop id and a user id. The token can be used in case the client is not able to store the basket id, but still needs to be able to reference a created basket via a unique client-generated id somehow.
The shop id can be used to create a basket that is connected to a specific shop. The direct effect of that is, that the API returns a checkout URL that points to the shop checkout. Omit the shop id, if you want to use the Spreadshirt platform (marketplace) checkout.
The user id can be used to connect the basket to a specific user. You can omit the user id by default.
- Basket Items: A basket can have, depending on its state, zero or more basket items. A basket item represents an abstract item added to the basket. Each basket item has a description, a quantity, a price, a shop id and a concrete basket item element.
The concrete basket item element has a type attribute, which can right now be set to the supported types sprd:article or sprd:product, and a xlink:href attribute which links the actual product or article that is available via the API. Depending on the type, one can set type specific element properties. In case of Spreadshirt article and product, these properties are size and appearance.
Please note that price and description are taken from the item linked by the basket item element. Quantity is always a value greater equal 1.
You can only add products or articles to a basket, if they are available in the desired size and appearance (see product’s product type stock states). Some products do not allow to change the default color (freeColorSelection = false) and thus can not be added to the basket in a different appearance than the configured one.
Continue reading “The Basket Model (API Terminology Explained #5)”