In my last blog post in the series “API Terminology Explained”, I explained the difference between product type, product and article. In this blog post, I will give you more details on our product type model.
Understanding the Product Type Model
In our terminology, a product type represents the pure piece or apparel, e.g. a T-shirt, as we get it from our supplier, e.g. American Apparel. A typical product type, e.g. a yellow T-shirt from American Apparel in size M, is illustrated in the picture above. A product type has the following characteristics:
- Core data: Each product type has a set of core data, such as name description and price.
- Appearances: A product type has one or more appearances. An appearance describes a pattern/color combination for a piece of apparel, e.g. a yellow T-shirt (no pattern/yellow color) or a camouflage T-shirt (camouflage pattern/light green and dark green as colors). It’s important to understand that we are not able to print with each available print type, e.g. flock, flex or digital direct, on each available product type. Therefore, we define for each appearance, which print types are allowed.
- Sizes: A product type has one or more sizes, such as S, M or L. Please note, that size information may vary between different product types. Sizes for adults are for example different from sizes for babys or kids.
- StockStates: Each product type provides stock state information for all allowed appearance/size combinations. We tell you for each combination, whether we have that in stock or not. Continue reading “The Product Type Model (API Terminology Explained #2)”
In this blog post, I will give you a short overview on the features provided by API v1, the technology behind API v1, the different parts of API v1 and the relationship to existing APIs.
API v1 is one part of our strategy to provide Customized Apparel as a Service (CAaaS) that I described in my previous blog post “Customized Apparel as a Service (CAaaS) at Spreadshirt”. Please note, that API v1 is right now Alpha, that means URL structures and XML payload might still change during the next releases. However, API v1 should be stable enough to allow you to build your first applications based on it. We will also keep you up to date on possible changes and new releases on this blog.
Today, API v1 provides the following features:
- Retrieve images for designs, products, product types, print types, etc.,
- Retrieve data for designs, products, articles, product types, print types, etc.,
- Create baskets and forward to Spreadshirt HTML checkout and
- Store and retrieve widget configurations.
For the next releases, we plan to provide the following features:
- Design upload and product creation,
- Design and article search for marketplace and
- Better basket integration.
Continue reading “Spreadshirt API v1 Explained”
We recently discovered a problem with queries in our Image API URLs. Unfortunately, our CDN provider – one of the big ones on the market – is not able to deliver images for URLs that contain queries in HTTP GET requests and vary the image appearance, e.g. the product color or image size, with that query. So URLs like
might not work correctly, because after a certain time the CDN delivers the wrong cached image for the given query parameters.
We asked our CDN provider to solve that problem, but apparently they are unable or unwilling to do so. The odd thing is that queries in URLs that return XML data work apparently. The reason for the problem seems to be an old Squid version for delivering image data in Europe. But we don’t know exactly.
Anyway, the workaround for the described problem is, that you put the query parameters in a comma-separated list behind the id, like