Why I need this is a bit complicated, and it's possible there is another way to do it with Awasu. (FYI, I was looking to use New2Web from Hexamail to do the same thing. In theory, I could have done it, but in execution New2Web seemed a bit flaky.)
I work for an organization that hopes to provide in inexpensive enterprise RSS solution. Users can subscribe to various "channels" (my term) in different categories. A channel will be composed of 1 to N feeds, perhaps with filters applied. For example, one category might be Industry. We might have 10 Industry channels, like Automotive. Automotive might consist of 3 different business feeds (New York Times, Wall Street Journal, etc.), and we might apply a filter like the word "car" or "automobile". These feeds are feeds that we subscribe to as an organization and are IP restricted. (B/c they are IP restricted, we can't use any SaaS solutions to reed RSS feeds.)
Each user would have a unique page on our intranet where they could view the channels they have subscribed to. They would also have the option of having their channel stories emailed to them once per day, at a time they select.
The team that administers the categories, channels and feeds would store all of this information in a database, or perhaps just in Awasu directly. If in a db, then a job would be run creating the channels in Awasu based on the feed info stored in the db.
We would also set up a subscription page on our intranet where users would indicate the channels they want to get and if they want the email version. This info would be stored in a db. Once or more per day a job would run that queries the db and creates a report based on each user's subscriptions, as those subscriptions could be updated regularly by users. Hence the need to create reports using an API, based on the db queries. It would be too much trouble to manually updated the reports in Awasu based on changes to subscriptions.
Does that make sense?