I want to decrease the number of API requests needed to save users time and server resources.

Use case: The user wants to see every information provided for a specific festival.

Problem: We need 50+ requests to fulfill this, depending on the size of the festival. See Wacken for example. Seven days with 10+ stages each.

Proposal: Include Sub- and Sub-Sub-Events (Main-Day-Stage) in lookup responses. Maybe a parameter for specifying the depth. It is important to have the event-artist rels included for each event. And maybe event-place rels as a bonus.

Is this even possible? How much work will it be?

I want to help as much as I can with implementing. The problem is, that I am more of a client/frontend developer. C#, WPF, Kotlin/Java, Android.... But I am willing to learn. My SQL knowledge is basic.