Wiki source code of Build your own shop system
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | If a standalone or [[JavaScript Integrated Shop>>url:https://help.spreadshirt.com/hc/en-us/articles/207487815-Website-Integration-with-JavaScript||shape="rect"]] does not fulfill your requirements and you absolutely must have a custom shop this tutorial aims to be a starting point for your journey. | ||
| 2 | |||
| 3 | == Example == | ||
| 4 | |||
| 5 | Before we start you can take a look at a working (minimal) example that we have built in order to demonstrate the capabilities of the Public Shop API: **[[https:~~/~~/github.com/spreadshirt/shop-api-example-integration>>url:https://github.com/spreadshirt/shop-api-example-integration||shape="rect"]]**. | ||
| 6 | |||
| 7 | [[image:attach:image2019-8-2_14-10-37.png]][[image:attach:image2019-8-2_14-11-14.png]][[image:attach:image2019-8-2_14-9-28.png]] | ||
| 8 | |||
| 9 | == Prerequisites == | ||
| 10 | |||
| 11 | We have to stress that you have to have a certain amount of time and technical knowledge in order to build your own shop based on the Public Shop API. | ||
| 12 | |||
| 13 | The following topics will not be covered by this tutorial and will be treated as given | ||
| 14 | |||
| 15 | 1. A Spreadshop with one or more design which you configured in the PartnerArea | ||
| 16 | 1. An Spreadshirt API Key | ||
| 17 | 1. HTML and CSS knowledge | ||
| 18 | 1. PHP and/or Javascript knowledge | ||
| 19 | 1. Basic understanding about HTTP and "REST Resources" (in combination often called API) | ||
| 20 | |||
| 21 | == Recommended approach == | ||
| 22 | |||
| 23 | === Manage your assets in the Partner Area === | ||
| 24 | |||
| 25 | After you have created your Spreadshop you are ready to manage your assets at any time in the Partner Area. This is the only supported way to manage your shops, designs and products. | ||
| 26 | |||
| 27 | === Import the data === | ||
| 28 | |||
| 29 | While it is possible to build a shop entirely using the Public Shop API as single source it is not recommended. You will not be able to introduce all kinds of filtering and sorting options because these are NOT built into the Public Shop API. | ||
| 30 | |||
| 31 | That means that you should (periodically) fetch all sellables via the Public Shop API and import them to YOUR database. Once you have imported this data you can build a frontend. The only thing that should require direct API access based on customer action is the Basket API. | ||
| 32 | |||
| 33 | \\ |