Hi Alvin Reyes , 

Thanks for the questions! Yeah, the idea is basically to add a custom backend API endpoint to work alongside the Core Service REST API, especially to make things easier for custom front-end apps on Experience Space.

I feel this idea could help both developers and the product in a few ways:

• We could have an integrated endpoint (within the context of Experience Space) that provides responses tailored to specific business needs.

  • This would let developers write custom logic (maybe using TOM.NET internally) to get the info they need without waiting on product updates.

  • It might also save costs since we wouldn’t need a separate hosting environment for these custom endpoints.

• Right now, doing bulk operations like downloading or uploading with conditional logic seems inefficient (though I might be wrong). It usually means many individual API calls, which can slow down the front end. Having a custom endpoint that handles bulk operations in one go could speed things up and reduce load.

Some examples of operations we could use custom endpoints for:

• Bulk updating metadata

• Sending notifications to business users once an operation completes

• Validating content in bulk for business processes

• Pulling reports for different types of schemas, publications, components, or pages

Using TOM.NET definitely makes sense since it already works well with Tridion Sites for custom requirements. But for easier front-end integration, building custom REST endpoints that use TOM.NET behind the scenes might keep things cleaner and improve the front-end developer experience.

Hope this helps explain the idea clearly!

Presumably this is for the Core Service REST API to work with Experience Space, Neetesh? What might be some good use cases for bulk operations? And is there a preference for the API for developing such extensions (TOM.NET itself)?

I can offer some ideas, but I'd like to hear what encouraged this idea from you and perhaps others that might be interested in such a feature.