Previously our community used one of the most popular API plugin for nopCommerce - https://www.nopcommerce.com/en/api-plugin. But it's a third-party plugin and the nop-templates team decided not to upgrade it to the latest version.
It's one of the most demanded features. That's why we consider implementing the API (by nopCommerce team)
AndreiMaz
All 4 comments
Can you elaborate more on
the nop-templates team decided not to upgrade it to the latest version
I've been following the upgrade path here , and there appears to be activity as of just a few days ago. If you're aware that this plugin is being abandoned, that would be critical information for us.
We're working on our initial version of nopCommerce and the API integration is a must. We've been preparing the site on version 4.2 since the API is supported there, with the hopes of upgrading to 4.3 before our first release. Our planning and timeline are clearly affected by this.
I will say that I feel the API belongs in the core product anyway. The API touches so many parts of the core, that version upgrades understandably take significant time to implement. Anyone using the API plugin is therefore forced to wait a good bit longer on version upgrade adoption.
brian-lagerman
on 28 Aug 2020
Hello there, I am currently searching for an e-commerce solution to integrate in our existing WCM system.
So I'm still in the process of digging through all the documentation and everything... so please correct me if I'm wrong.
Looking at the aforementioned API-plugin I indeed wonder if there is no "built-in/supported" option to integrate nopCommerce into existing WCM deployments on an API-only level ("headless"). I'm just watching the youtube video where that guy praises the architecture in the highest tones. But reading this issue makes me wonder if the "backend" is tightly coupled to the "frontend" which is of course perfectly ok, just not the solution I am looking for.
naymore
on 2 Sep 2020
I'm currently looking into headless alternatives to nopCommerce. It would be awesome if nopCommerce adds a headless option.
P-de-Jong
on 28 Sep 2020
For us it's a deal breaker if the API is not provided ASAP
eadameg
on 20 Dec 2020
Related issues
tigran-avdalyan
路
5Comments
AndreiMaz
路
3Comments
AndreiMaz
路
3Comments
mariannk
路
4Comments
DmitriyKulagin
路
5Comments
Most helpful comment
Can you elaborate more on
I've been following the upgrade path here , and there appears to be activity as of just a few days ago. If you're aware that this plugin is being abandoned, that would be critical information for us.
We're working on our initial version of nopCommerce and the API integration is a must. We've been preparing the site on version 4.2 since the API is supported there, with the hopes of upgrading to 4.3 before our first release. Our planning and timeline are clearly affected by this.
I will say that I feel the API belongs in the core product anyway. The API touches so many parts of the core, that version upgrades understandably take significant time to implement. Anyone using the API plugin is therefore forced to wait a good bit longer on version upgrade adoption.