An internet search turns up HebCalVb6, a VB6/VBA module to demonstrate how to convert a Hebrew date into the Gregorian date. It can be used within Visual Basic or within a Excel Macro. 

http://www.dafaweek.com/HebCal/HebCalVb6.php

Hi, it has been a couple of weeks and the Google Calendar cache appears to have cleared by now. We have checked and can confirm that Google Calendar is displaying this feed through December 31, 2024.

Excellent. Glad this helped. Good luck!

Glad you got it working!

Our API tries to be very open when it comes to CORS. We always include Access-Control-Allow-Origin: * in the response when the cfg parameter is set to json.

No authentication or authorization is required to use our API. It is accessible to a wide range of users without restrictions.

We've added a new script without nikkud

<script src="https://www.hebcal.com/etc/hdate-he-v2.js"></script>

Confirmed that 365 days will fit in the Google Calendar feed limit. We pushed out a change, and depending on Google's caching it may take between 1-7 days before you see the refreshed year-long feed updated on Google Calendar.

We have made the change to the website.

Please note that results for year 1752 C.E. and earlier may be inaccurate.

Hebcal does not take into account a correction of ten days that was introduced by Pope Gregory XIII known as the Gregorian Reformation. ^[1]

You're welcome. There's a limit on how many events Google Calendar can accept in an iCalendar feed. We can experiment a bit - my guess is that we might be able to expand it to 90 days, possibly an entire year if it fits within Google's limits.

Hi, thanks for using Hebcal. Yes, it's possible to replace our links with your own using a bit of custom JavaScript.

If you are using the FullCalendar integration, you can replace the events JSON feed URL with a JavaScript function

https://fullcalendar.io/docs/events-function

Inside the function you'll want to fetch our event feed (taking care to append the info.start and info.end parameters at the end of the URL as ISO 8601 strings), and then use JSON.parse to convert the entire feed into an array of event objects. Then iterate through the array, and either delete the url field or replace it with one that points to your own website.

Does this answer your question?

Thanks for the suggestion. We will look into making this change.