I have one API ( voice , mvb, accessories products ) I want to fetch the all the product details form api to aem & storage the product details in node level (Json format ) and creating product components process steps
A few comments have been already made, but I want to give you my view on it.
In short: if it's possible avoid it. Because you will end up with topics like:
how do I structure that data in the repository, so it's not getting slow (too many siblings), and that you don't need search for all operations on it.
Witih your approach you are creating a cache. On product changes how long does it take to propagate changes from the backend to your AEM? Next consider that from end-to-end (changes in the PIM until a enduser can see the changed data), and calculate both the minimum and maximum delay. Is that acceptable?
What about deleting entries from this cache?
In many cases it might be best if you either bypass AEM when you need to display product information (and let the frontend reach out to the PIM directly). You can look at the current Commerce Integration Framework (CIF2) of Adobe; of course this is for a shopping solution, but also for a shop displaying products is a big topic.
Hope to give you some inspiration what to look for.
You can write a scheduler(if you want to pull the updated content on a regular basis) and a java service that will pull the data from REST endpoint and save it in JCR(you can use service user). Let us know what exactly are you looking for, some one from the community will definitely be able to help you.
You can definitely fetch the product details from API and store it in node level. You can get the response in JSON format by makunf REST call and create json files response at node level in AEM. Try using service user for accessing.
You can write a servlet. , which can consume the API end point and parse the entire json and then for each product it can create a node in the JCR using various API.
It would be great if you share more details on how you want to create a product component.
Note: Rather create one node per product , you can also create one content per product . Also you can share an API in AEM which will create a product in AEM. And the logic of parsing the API end point can be out side AEM which can at-last call the AEM end point to store the products alone.