"next ocurence(s)" of repeating items in API

[leoley]

Hello DJSoft !

i'm about to build the new website for a radiostation using RadioBoss !

i am trying to build a CMS that is automatically producing articles on the website, depending on the RadioBoss Schedule.

Unfortunately i cannot find any value in the API that would be able to tell the NEXT OCURENCE of a repeating item/podcast.
I would need this very much to automatically produce pages for future scheduled podcasts, so that users can upload their podcast via the precreated page in the cms and then radioboss will read the file via a rss stream.

in the schedule API i can only find the ocurence with its repeating mechanism but not a concrete next ocurence date and time.

Would there be any possibility to add a "next ocurence" or even "next ocurences" of a repeating item to the API ?

Kind regards
Leo

 

[djsoft]

Would there be any possibility to add a "next ocurence" or even "next ocurences" of a repeating item to the API ?

It doesn't evaluate the next time a track would play. Using the scheduler API you can check what events are going to run soon (within 24 hours) and based on that, you can check the event's action to see what it starts.

The rest depends on how you run the episodes. If you use the Track List, there's no API to check what next episode it will select.

 

[Radio-Albena]

Hello DJSoft !

i'm about to build the new website for a radiostation using RadioBoss !

i am trying to build a CMS that is automatically producing articles on the website, depending on the RadioBoss Schedule.

Unfortunately i cannot find any value in the API that would be able to tell the NEXT OCURENCE of a repeating item/podcast.
I would need this very much to automatically produce pages for future scheduled podcasts, so that users can upload their podcast via the precreated page in the cms and then radioboss will read the file via a rss stream.

in the schedule API i can only find the ocurence with its repeating mechanism but not a concrete next ocurence date and time.

Would there be any possibility to add a "next ocurence" or even "next ocurences" of a repeating item to the API ?

Kind regards
Leo

Hi Leo,

just as a possible workaround: I had a similar requirement and built a small RadioBOSS-specific scheduler tool that calculates the next occurrences of repeating events itself, including dates beyond the 24-hour window available through the API.


I described it here in the forum:
https://www.djsoft.net/community/th...heduler-for-radioboss-free-open-source.15651/


It may be useful for what you are trying to achieve with your CMS.


Kind regards,
Raymundus

 

[Radio-Albena]

Hello DJSoft !

i'm about to build the new website for a radiostation using RadioBoss !

i am trying to build a CMS that is automatically producing articles on the website, depending on the RadioBoss Schedule.

Unfortunately i cannot find any value in the API that would be able to tell the NEXT OCURENCE of a repeating item/podcast.
I would need this very much to automatically produce pages for future scheduled podcasts, so that users can upload their podcast via the precreated page in the cms and then radioboss will read the file via a rss stream.

in the schedule API i can only find the ocurence with its repeating mechanism but not a concrete next ocurence date and time.

Would there be any possibility to add a "next ocurence" or even "next ocurences" of a repeating item to the API ?

Kind regards
Leo

Hi Leo,

I think I understand what you are trying to achieve now.

You do not actually need RadioBOSS to create the future CMS pages itself.

I am currently developing a small WebSync application for RadioBOSS. It reads the RadioBOSS scheduler locally and exports the schedule to JSON, including the calculated next occurrences of repeating events. The JSON can then automatically be uploaded to your web server.

Your CMS could simply read that JSON and create the future podcast upload pages from it.

For example, WebSync could provide something like:

{
"name": "Rock Talk",
"next_occurrences": [
"2026-09-21T18:00:00",
"2026-09-28T18:00:00",
"2026-10-05T18:00:00"
]
}
Your PHP CMS could then automatically create:

• Rock Talk – 21 September – Upload episode
• Rock Talk – 28 September – Upload episode
• Rock Talk – 5 October – Upload episode

The podcaster uploads the episode to your CMS, your CMS adds it to the podcast/RSS feed, and the existing repeating RadioBOSS event can play that feed or URL at the scheduled time.

So the workflow would basically be:

RadioBOSS Scheduler → WebSync → JSON on web server → your CMS → podcast upload page

This also means your CMS does not need direct access to the RadioBOSS API or to the studio PC.

The scheduler itself remains read-only from the web side; WebSync only exports the schedule.

I am still testing the WebSync application, but this exact use case is one of the reasons I added future occurrences for repeating scheduler events.

Kind regards

Raymond