Pages APIs

Great, Thanks Cristinel, the reason I thought to mention it because that will solve few communications across. I remember ages ago I have requested to add a functionality so when Catalogues or Pages are updated (url/name wise), their associated menus get updated as well, because we had to travel manually to edit them, well, with exposing the menus in conjunction with pages and eCommerce APIs, we can create Apps that communicate that way directly, when a page or a catalogue is updated, we can trigger an automatic update to their associated menus.

[Added]: Also I think exposing Menus APIs will take less time than completing other complex areas such eCommerce and CRM, after all, the Pages APIs were added in no time and those are bigger than menus.

I hope you guys can get this out soon. But overall, so far I am impressed by the work you guys are doing.

Thank you

All good Cristinel, a Use Case as provided in my previous reply:

As an Example: At the moment, if you add a Catalogue or a Page or any element in this instance, or sometimes when you're forced to change the URL of those elements for some reason, you have to go back to the Menus and make your edits.

With the ability of creating Apps for the above, we can just make a Post call to make the necessary updates to the menus in accordance to the updates made to the elements in question. No need to go back and forth to the Menus to update them. Automating as much as possible, provides an impression of solid communication in a system. it will make all parties life easier at some extent.

@ Liam, I know it is possible as you said, that is how we have it setup for an App at this moment, but having the Menu APIs opened is much easier to just target it rather than creating a WebApp etc... Plus I don't see any harm of having the Menus APIs.

In this instance I'm referring to more Menu APIs in conjunction with the Pages APIs

Not in the case of this project, we need an App because the management of the content is different from a typical situation, and more complex, so we had to build a custom functionality to allow for the requirement. This is not a typical use of an App. We didn't just build it because we wanted to do an App, trust me building an App for a requirement is our last resort, if we can do something natively with BC, that will be our first attempt. I can't go through details, but this project need an App for that purpose