I note that you designate the Haftarah of Shabbat Shuvah as comprising all three of the selections from Hosea, Micah, and Joel.  But that apparently wasn't a widespread traditional haftarah selection, and may be current solely based on a misunderstanding of the intent of the Hertz Humash.  See the article, "The Haftarot of Etz Hayim: Exploring the Historical Interplay of Customs, H.umashim, and Halakhah" by Rabbi David E. S. Stein in  Conservative Judaism 54/3 (Spring 2002)

hi Support, 

The Webservice answer is incorrect...

We are posting http://www.hebcal.com/hebcal/?v=1&cfg=json&maj=off&min=off&mod=off&nx=off&year=2018&month=12&ss=off&mf=off&c=on&geo=geoname&geonameid=3448439&m=0&b=30&s=off

It's returning:

{"category":"candles","hebrew":"הדלקת נרות","date":"2018-12-05T20:33:00-02:00","title":"Candle lighting: 8:33pm"}

8:33pm

Should be 7:33pm  

take a look at https://www.timeanddate.com/sun/brazil/sao-paulo the sunset expected to 7:55pm. 

Thanks you in advanced! 

"Modern holidays" is missing 30 November, which has been in place since 2014 ... https://mfa.gov.il/MFA/AboutIsrael/Spotlight/Pages/The-Jewish-Refugees-from-Arab-Countries.aspx 

Thanks for your great service.

Hebcal successfully installed on my desktop, but does not sync with Google calendar on my Android. All other items of calendar sync successfully

I created a calendar for 2019 but there are no candle-lighting times or havdalah listed for any shabbos or yom tov. Is anyone else experiencing this issue?

The HebCal Smartthings integration changes modes based on the candle lighting time provided by the HebCal API. The smart app code can be seen here. Recently I noticed that the smart app is switching to Sabbath mode at candle lighting time on Chanukah due to chanukah candles being listed under the "candles" category. Because of the way the JSON is parsed this is causing the smart app to trigger Sabbath mode at candle lighting time during Chanukah. 

I'm not saying this is an API issue because it can be resolved by changing the app's programing, but since there are many people using this Smartthings smart app (which is an official app available in the Smartthings store)  perhaps the API could be slightly adjusted so as to avoid this error?