How to speed up your app with API caching [Magento & PrestaShop]?

How to speed up your app with API caching [Magento & PrestaShop]?

App response time matters. To optimize your app response time, JMango360 supports API caching to improve data communication between our plugin and your server.

API caching is made available to Magento (Native & PWA) and PrestaShop (Native & PWA).

How API caching works?

API caching reduces the number of requests a server needs to process, in turn reducing data loading times. The idea is that when a mobile customer visits a certain page for the first time the app stores the rendered page (caching). When the second request for the same page is made, the app just serves the saved response. 

As we calculate, the API is delivered significantly faster when cached. With caching, while the first request for a product list or product details might take up to 4 or 6 seconds, the next requests to the same page only require up to 2 seconds.

You need to manually enable API caching in your Magento or PrestaShop backend. Once enabled, API cache will be cleared if its lifetime is expired (default lifetime is 3600 seconds) or if you make any changes to the product attributes such as product name, image, and price. API cache can also be set to be cleared based on order placement on app.

Magento 2

Required plugin versions: Native - 1.8.3, PWA - 1.2.0



Step 1: In Magento Admin, go to System > Tools > Cache Management, then enable JMango360 API cache.
Step 2: In Magento Admin, go to Stores > Settings > Configuration. Under Services, select JMango360 Mobile.
Step 3: Under Developer, enable Enable API Caching.
  1. Cache lifetime: Default value is 3600 seconds. You can change the lifetime as you'd like.
  2. Behave on a new order: Choose one of the following three options.
    1. Always clear product cache: Default option. Cache will always be cleared whenever a new mobile order is placed.
    2. Do not clear product cache: Order placement does not affect cache lifetime.
    3. Clear if the product is out of stock: Cache will be cleared when an order placement makes a product sold out. 
Step 4: Click Save Config to finish.

Magento 1

Required plugin versions: Native - 4.0.38, PWA - 1.1.3



Step 1: In Magento Admin, go to System > Cache Management, then enable JMango360 API cache.
Step 2: In Magento Admin, go to JMango360 > Settings.
Step 3: Under Developer, enable Enable API Caching.
  1. Cache lifetime: Default value is 3600 seconds. You can change the lifetime as you'd like.
  2. Behave on a new order: Choose one of the following three options.
    1. Always clear product cache: Default option. Cache will always be cleared whenever a new mobile order is placed.
    2. Do not clear product cache: Order placement does not affect cache lifetime.
    3. Clear if the product is out of stock: Cache will be cleared when an order placement makes a product sold out. 
Step 4: Click Save Config to finish.

PrestaShop 1.7

Required plugin versions: Native - 1.21.6, PWA - 1.1.3



Step 1: In PrestaShop Backend, go to Shop Parameters > JMango360 Settings.
Step 2: Under API Caching, turn on Enable API Caching.
  1. Cache lifetime: Default value is 3600 seconds. You can change the lifetime as you'd like.
  2. Behave on a new order: Choose one of the following three options.
    1. Always clear product cache: Default option. Cache will always be cleared whenever a new mobile order is placed.
    2. Do not clear product cache: Order placement does not affect cache lifetime.
    3. Clear if the product is out of stock: Cache will be cleared when an order placement makes a product sold out. 
Step 3: Click Save to finish.

PrestaShop 1.6

Required plugin versions: Native - 1.21.6, PWA - 1.1.3



Step 1: In PrestaShop Backend, go to Preferences > JMango360 Settings.
Step 2: Under API Caching, turn on Enable API Caching.
  1. Cache lifetime: Default value is 3600 seconds. You can change the lifetime as you'd like.
  2. Behave on a new order: Choose one of the following three options.
    1. Always clear product cache: Default option. Cache will always be cleared whenever a new mobile order is placed.
    2. Do not clear product cache: Order placement does not affect cache lifetime.
    3. Clear if the product is out of stock: Cache will be cleared when an order placement makes a product sold out. 
Step 3: Click Save to finish.

    • Related Articles

    • Video Tutorials - Create Your Integrated App

      Create a Magento 2 App Create a BigCommerce App Create a Lightspeed App Create a PrestaShop 1.7 App PrestaShop 1.7: Share backend access with JMango360 Create a PrestaShop 1.6 App PrestaShop 1.6: Share backend access with JMango360 ​

    • New features & updates

      New features & updates In this article, you’ll find our key technical updates and new features for our app products grouped by quarter. Discover new possibilities to improve your app. If you see any interesting features or you have questions, please ...

    • Speed up order processing with product scanner B2B [Magento & Lightspeed]

      Besides Product Scanner B2C for individual buyers, JMango360 is glad to introduce Product Scanner B2B for business buyers who want to speed up their large quantity orders. The B2B scanner is sure to save you a great deal of time and taps compared to ...

    • Magento 2: Configure the plugin

      After you install the JMango360 plugin successfully on your Magento 2 webshop, please go to Magento Admin > Stores > Configuration > Services > JMango360 Mobile to configure the plugin. Connection Credentials Version: The version of the plugin. User ...

    • Magento: It says 'Access denied. Please check the API Username and API key.' when opening product catalog

      Issue When you open product catalog, your app shows an error message 'Access denied. Please check the API username and API key' and does not work anymore. Cause The issue happens because the API username and/or API key in your website backend and ...