API Integration (Basket)

Please check the API Reference for all technical details about the API.

The API was designed to make the integration for developers as easy as possible. However, the handover of the product data from 35up to your backend requires additional coding on your side when you use the API. The additional 35up product, from this point on, needs to be present in your database.

Best Practices

To achieve the handover using the standard processes that most shop systems use seems to be the easiest, cleanest approach. Of course, the exact execution depends on your system and your system conditions. Here, we identify three best practices:

Configurable Products

Many modern shop systems provide the ability to add "configurable" products into the basket. These products do not have to preexist in your product database — they can be created "on the fly." This mechanism is perfect for adding 35up cross-selling to the basket and handing over the data to your backend. In this case, you simply create a new configurable product every time a customer adds a 35up product to the basket and enrich the necessary information based on the product data provided.

This approach ensures the sole use of standard processes and is not likely to require additional changes on the backend.

Dummy Products

Another approach to hand over the product data from the front end to the backend is the use of dummy products. If your shop system does not allow for configurable products, dummy products are very often the next best choice. In this case, you create one "35up dummy" product in your product database. Every time a 35up product is added to the basket, you add this dummy product and overwrite the price and name with the values from the product info.

Order Attributes

If neither the configurable nor the dummy product approach works for your system, you could add the additional cross-selling items as attributes or comments to an order. In this case, make sure that the information is stored in a structured, repeatable way and that you can use the values to calculate the final price.

Get Product Info

To support your effort in handing over the product data, we created an additional API endpoint: "GET products."


This endpoint provides you with all product information based on the SKU. With this endpoint, you only have to hand over the SKU and the quantity, and you can reach all other information on demand later.

 "recommendations": [
     "vendor": {
       "legalName": "caseable GmbH",
       "name": "caseable",
       "logo": {
         "square": "https://media.caseable-stage.de/ logo/squared.png",
         "landscape": "https://media.caseable-stage.de/ logo/horizontal.png"
       "id": "caseable"
     "sku": "caseable/ PF165XXC01737XXAPIP65",
     "price": {
       "value": 19.9,
       "formatted": "$ 19.90",
       "currency": "USD"
     "name": "Apple iPhone 11 Pro Max Eco Friendly Phone Case, \ "Eco-Design\" by caseable Designs",
     "images": {
       "thumbnail": "https://caseable.com/ media/catalog/product/ thumbnail/ apple-iphone-11-pro-max- eco-friendly-phone-case/ caseable-designs/ eco-design.jpg"
     "descriptions": {
       "short": "Design protection for your device",
       "long": "This accessory from caseable not only looks great, but also protects your device all around. caseable produces environmentally on order and is known for its great artist designs."
     "delivery": {
       "timeMin": 5,
       "timeMax": 8
     "actions": {}

The JSON response always provides the following information, which can be used to store the product with all its details in your product database:.

Vendor Information

For every vendor, the vendor object provides:

  • LegalName: The legal name of the entity, as displayed on invoices
  • Name: The name that the customer sees
  • Logo: A URL to a logo image file in squared (portrait) and landscape mode - This image can be used if you want to show the vendor’s logo to the customer.
  • ID: The internal vendor ID on our platform

Product Information

The SKU string shows the unique identifier of a product on our platform.

The price object provides following information:

  • Value: Numeric value of the price, for calculations
  • Formatted: The numeric value in the correct format to display to the customer
  • Currency: The three-letter ISO code for the price currency

The name string shows the full name of the product.

Images provides a number of product image URLs, with the required "thumbnail."

The descriptions object provides:

  • Short: A one-line description of the cross-selling product, to introduce it without going into much detail
  • Long: A longer description of the product, to create a detailed overlay in the widget

The delivery object provides two data points on the delivery time:

  • TimeMin: The minimum delivery time in days
  • TimeMax: The maximum delivery time in days