If you are currently running a custom system based on a Legacy User Area (LUA) shop, your account will be migrated to the Partner Area (PA) mid of September. Unfortunately for you, the PA is not just another frontend, but the domain entities we work with are slightly different and slightly different API endpoints have to be used. Your integration has thus to be adjusted to keep working.

Which parts of Spreadshirt's API are still valid and what exactly changed?

The good news is that the vast majority of the domain entities and their corresponding REST resources were not changed. They are still valid and work like they used to. However, articles and articleCategories became obsolete and will stop working once you are migrated. Products still exist, but they should not be worked with directly anymore when developing an online shop integration. Use ideas and sellables (sic!) instead as described here.

These new entities can be characterized as follows:

A sellable is thus something concrete that a customer can buy, while an idea represents a grouping of content mainly intended to make administration easier.

Basket resources

The basket resources generally still work as they used to. However, keep in mind that only sellables can be added to a basket.
If your basket implementation is still XML based on you do not want to rework it entirely, just adapt your requests to use this payload fragment instead:

<element id="MLorqlGGrLhljORQ7old-1007-22" type="sprd:sellable">
      <property key="appearance">539</property>
      <property key="size">3</property>
   <shop id="100229382" href=""/>

Note that the type property needs a different constant now and a shop tag needs to be sent as well.

Legacy article mapping resource

You may still have deeplinks or internal data structures referencing the soon-deleted articles.
To ease the transition phase, we provide the following resource that allows you to find the corresponding sellable your article was migrated to:


The response contains the identifiers necessary to make the connection between old and new domain entities.

    "ideaId": "5d0a19935fd3e41d7dd6900f",
    "productTypeId": "725",
    "sellableId": "R43XoE5rBATzxQnRNykG-725-9"

This is too abstract for me. Do you have code examples available?

Yes, there is an example integration of this API available here.
It shows a draft of a shop system written in php that might be helpful to understand the (list-page -> detail-page -> add-to-basket) workflow.

Updating Data

There is no Public API available for uploading or updating ideas or sellables. This should be done via Partner Area.
Note that not only the content you upload in the Partner Area, but also the shop settings affect the output of the sellable resources. For example, enabling model images affects the image URLs returned by the API.

Will the design resources keep working?

Yes. Every idea and sellable references a design. The designs can thus be considered an alternative view on the data you manage in the Partner Area. However, in standard implementations, using these resources should not be necessary.

My account is still User Area based. How do I test my integration before I get migrated?

If you do not own a Partner Area based shop yet, but need something "in hand" to develop your implementation, you can rely on the example shop 100488332 provided by us. The shop is available on the European platform (.net) only. You can use articleId=999999999 to test the legacy article mapping resource in this shop.

I am using a non-official designer-tool integration. How can I enable editing of sellables for my customers?

The designer tool can be bootstrapped with a parameter named sellableId. This will only work in Sketchomat/Smartomat, but not in Tablomat. Alternatively, bootstrapping the tool with productType & design still works.