<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Mobiscroll Connect release notes — API and SDK changelog</title><description>Every Mobiscroll Connect release: changes to the calendar sync API and to its Node.js, PHP, .NET, Python, Java, Go and Ruby SDKs, version by version.</description><link>https://mobiscroll.com/releases/connect</link><language>en-us</language><item><title>Mobiscroll Connect API 1.6.1</title><link>https://mobiscroll.com/releases/connect#api-v1.6.1</link><guid isPermaLink="false">1.6.1</guid><description>&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;p&gt;Subscriptions, deliveries and their payloads are corrected.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;p&gt;Event responses, free-busy results and request validation are corrected.&lt;/p&gt;
&lt;h3&gt;iCloud and CalDAV&lt;/h3&gt;
&lt;p&gt;Conference URLs, event IDs and updates are corrected for both providers.&lt;/p&gt;
&lt;h3&gt;Disconnect and revoke&lt;/h3&gt;
&lt;p&gt;Both endpoints handle more cases correctly.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;url&lt;/code&gt;, the join URL, to &lt;code&gt;conferenceData&lt;/code&gt; in &lt;code&gt;GET /api/events&lt;/code&gt;, in the &lt;code&gt;POST&lt;/code&gt; and &lt;code&gt;PUT /api/event&lt;/code&gt; responses and in webhook deliveries.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;original&lt;/code&gt; to &lt;code&gt;conferenceData&lt;/code&gt; in the same responses and deliveries: the conference data exactly as the calendar provider returns it, Google&amp;rsquo;s &lt;code&gt;conferenceData&lt;/code&gt; or Microsoft&amp;rsquo;s &lt;code&gt;onlineMeeting&lt;/code&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;GET /api/events&lt;/code&gt; with the &lt;code&gt;free-busy&lt;/code&gt; scope returning the &lt;code&gt;description&lt;/code&gt; of Outlook, iCloud and CalDAV events and the &lt;code&gt;conference&lt;/code&gt; of CalDAV events. Both are now left out, as &lt;code&gt;description&lt;/code&gt; already was for Google.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed iCloud and CalDAV URLs set in Apple Calendar missing from &lt;code&gt;conference&lt;/code&gt;. They are now returned in &lt;code&gt;conference&lt;/code&gt; and &lt;code&gt;conferenceData&lt;/code&gt;, as URLs set through Connect already were.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; The &lt;code&gt;conference&lt;/code&gt; of an iCloud or CalDAV event is the URL set on the event. It can be any URL, not only a meeting link.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;PUT /api/event&lt;/code&gt; changing the iCal UID of an iCloud or CalDAV event. An iCloud event got its &lt;code&gt;id&lt;/code&gt; followed by &lt;code&gt;@mobiscroll.com&lt;/code&gt; as the UID, and a CalDAV event got the &lt;code&gt;eventId&lt;/code&gt; of the request. The event now keeps the UID it already has.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;GET /api/events&lt;/code&gt; answering &lt;code&gt;500&lt;/code&gt; when &lt;code&gt;calendarIds&lt;/code&gt; or &lt;code&gt;nextPageToken&lt;/code&gt; is not valid JSON. It now returns &lt;code&gt;400&lt;/code&gt; with an &lt;code&gt;error&lt;/code&gt; naming the parameter.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;POST /api/subscribe-webhook&lt;/code&gt; replacing another user&amp;rsquo;s subscription when called with that subscription&amp;rsquo;s &lt;code&gt;channelId&lt;/code&gt;, so its owner stopped receiving webhooks. It now returns &lt;code&gt;409&lt;/code&gt; with &lt;code&gt;{ &quot;error&quot;: &quot;channelId is already in use&quot; }&lt;/code&gt; and leaves the other subscription untouched.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;POST /api/oauth/disconnect&lt;/code&gt; with &lt;code&gt;account&lt;/code&gt; stopping only the webhook subscription of the Google primary calendar. It now stops the subscription of every calendar on that account, except a calendar that another connected account of the same provider can see. See &lt;a href=&quot;/docs/connect/api/oauth#endpoint-disconnect&quot;&gt;Disconnect Account&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed some calendar changes being delivered twice, when several provider notifications for one calendar arrived close together and when overlapping connects of the same account created two subscriptions for one calendar. Connect now fetches the changes of a calendar one batch at a time and keeps one subscription per calendar and user.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed deleted Outlook, iCloud and CalDAV events arriving in webhook deliveries without &lt;code&gt;calendarId&lt;/code&gt;. Every delivered event now has it.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;conferenceData&lt;/code&gt; to webhook deliveries. Every event that has a conference now carries it, in the shape &lt;code&gt;GET /api/events&lt;/code&gt; returns. See &lt;a href=&quot;/docs/connect/api/webhooks#webhook-delivery-payload&quot;&gt;Client webhook payload&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed iCloud and CalDAV event ids in webhook deliveries differing from &lt;code&gt;GET /api/events&lt;/code&gt;, so a deleted event or series could not be matched to its earlier deliveries. Created and updated iCloud events, and the &lt;code&gt;PUT /api/event&lt;/code&gt; response for an iCloud event, used the iCal UID as &lt;code&gt;id&lt;/code&gt;; deleted CalDAV events used the file name of the calendar object. They now use the &lt;code&gt;id&lt;/code&gt; of &lt;code&gt;GET /api/events&lt;/code&gt;: the file name for iCloud and the iCal UID for CalDAV. A deleted CalDAV event arrives with the file name only until Connect has recorded the UID of its calendar object, at its next check of the calendar.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;POST /api/oauth/revoke&lt;/code&gt; with an expired access token returning &lt;code&gt;200&lt;/code&gt; without revoking anything, so the refresh token kept working. It now revokes the user&amp;rsquo;s access and refresh tokens. See &lt;a href=&quot;/docs/connect/api/oauth#endpoint-revoke&quot;&gt;Revoke Token&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;POST /api/oauth/disconnect&lt;/code&gt; accepting any &lt;code&gt;provider&lt;/code&gt; value. A missing or unknown &lt;code&gt;provider&lt;/code&gt; now returns &lt;code&gt;400&lt;/code&gt; with &lt;code&gt;{ &quot;error&quot;: &quot;Missing or invalid provider&quot; }&lt;/code&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Node.js SDK 1.6.1</title><link>https://mobiscroll.com/releases/connect#nodejs-sdk-v1.6.1</link><guid isPermaLink="false">nodejs-sdk-1.6.1</guid><description>&lt;h3&gt;Event types&lt;/h3&gt;
&lt;p&gt;Event dates are typed as the ISO strings the SDK returns.&lt;/p&gt;
&lt;h3&gt;Missing API features&lt;/h3&gt;
&lt;p&gt;Revoke, calendar &lt;code&gt;account&lt;/code&gt; and &lt;code&gt;readOnly&lt;/code&gt;, meeting fields on event writes and the &lt;code&gt;theme&lt;/code&gt; option are now covered.&lt;/p&gt;
&lt;h3&gt;Webhook types&lt;/h3&gt;
&lt;p&gt;Webhook event types now match what a delivery carries.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed the &lt;code&gt;EventCreateData&lt;/code&gt; and &lt;code&gt;EventUpdateData&lt;/code&gt; types missing &lt;code&gt;conference&lt;/code&gt; and &lt;code&gt;conferenceData&lt;/code&gt;, so TypeScript rejected &lt;code&gt;{ autoGenerate: true }&lt;/code&gt; in an object literal. The SDK already sent both fields at runtime.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;url&lt;/code&gt; and &lt;code&gt;original&lt;/code&gt; to the &lt;code&gt;ConferenceData&lt;/code&gt; type. The API returns both from 1.6.1.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed the declared type of &lt;code&gt;start&lt;/code&gt; and &lt;code&gt;end&lt;/code&gt; on events from &lt;code&gt;events.list()&lt;/code&gt;, &lt;code&gt;events.create()&lt;/code&gt; and &lt;code&gt;events.update()&lt;/code&gt;. It is now &lt;code&gt;string&lt;/code&gt;, the ISO 8601 strings the SDK returns; it was &lt;code&gt;Date&lt;/code&gt;, so calling &lt;code&gt;Date&lt;/code&gt; methods on them threw.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed the &lt;code&gt;Calendar&lt;/code&gt; type missing &lt;code&gt;account&lt;/code&gt; and &lt;code&gt;readOnly&lt;/code&gt;. Both were already present at runtime.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed the return type of &lt;code&gt;verifyWebhook()&lt;/code&gt; declaring &lt;code&gt;start&lt;/code&gt; and &lt;code&gt;end&lt;/code&gt; as &lt;code&gt;Date&lt;/code&gt;. They are typed &lt;code&gt;string&lt;/code&gt;, the ISO 8601 strings the SDK returns.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; &lt;code&gt;WebhookEvent.original&lt;/code&gt; is now typed optional: deleted Outlook, iCloud and CalDAV events in a &lt;code&gt;verifyWebhook()&lt;/code&gt; delivery arrive without it.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed the type of &lt;code&gt;WebhookEvent.conference&lt;/code&gt;, which was declared &lt;code&gt;string&lt;/code&gt;. It is now &lt;code&gt;WebhookConference&lt;/code&gt;, the object a &lt;code&gt;verifyWebhook()&lt;/code&gt; delivery carries, with &lt;code&gt;url&lt;/code&gt;, &lt;code&gt;provider&lt;/code&gt;, &lt;code&gt;meetingProvider&lt;/code&gt; and &lt;code&gt;data&lt;/code&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; &lt;code&gt;WebhookEvent.lastModified&lt;/code&gt; is now typed as always present: every event in a &lt;code&gt;verifyWebhook()&lt;/code&gt; delivery has it.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;auth.revoke()&lt;/code&gt;, which revokes every access and refresh token of the user through &lt;code&gt;POST /api/oauth/revoke&lt;/code&gt;. See &lt;a href=&quot;/docs/connect/api/oauth#endpoint-revoke&quot;&gt;Revoke Token&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;generateAuthUrl()&lt;/code&gt; not accepting &lt;code&gt;theme&lt;/code&gt;. It now accepts &lt;code&gt;light&lt;/code&gt;, &lt;code&gt;dark&lt;/code&gt; or &lt;code&gt;auto&lt;/code&gt;, which sets the color scheme of the Connect pages.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect PHP SDK 1.6.1</title><link>https://mobiscroll.com/releases/connect#php-sdk-v1.6.1</link><guid isPermaLink="false">php-sdk-1.6.1</guid><description>&lt;h3&gt;Event writes&lt;/h3&gt;
&lt;p&gt;Creating and updating an event returns the event instead of raising an error.&lt;/p&gt;
&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;Deliveries with a meeting on an event now verify.&lt;/p&gt;
&lt;h3&gt;Missing API features&lt;/h3&gt;
&lt;p&gt;Revoke, calendar &lt;code&gt;account&lt;/code&gt; and &lt;code&gt;readOnly&lt;/code&gt; and the &lt;code&gt;theme&lt;/code&gt; option are now covered.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;account&lt;/code&gt; and &lt;code&gt;readOnly&lt;/code&gt; to &lt;code&gt;Calendar&lt;/code&gt; objects. The API returns both for every calendar.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;events()-&amp;gt;create()&lt;/code&gt; and &lt;code&gt;events()-&amp;gt;update()&lt;/code&gt; throwing &lt;code&gt;ServerError&lt;/code&gt; on every successful write. They now return the written event.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;verifyWebhook()&lt;/code&gt; rejecting every delivery whose events include a conference, with reason &lt;code&gt;invalid_payload&lt;/code&gt;, because a delivery carries &lt;code&gt;conference&lt;/code&gt; as an object. Those deliveries now verify: &lt;code&gt;$conference&lt;/code&gt; is the join URL of that object, and &lt;code&gt;$conferenceData&lt;/code&gt; is the delivery&amp;rsquo;s &lt;code&gt;conferenceData&lt;/code&gt;, or one built from the object when the delivery has none.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;auth()-&amp;gt;revoke()&lt;/code&gt;, which revokes every access and refresh token of the user through &lt;code&gt;POST /api/oauth/revoke&lt;/code&gt;. See &lt;a href=&quot;/docs/connect/api/oauth#endpoint-revoke&quot;&gt;Revoke Token&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;generateAuthUrl()&lt;/code&gt; not accepting &lt;code&gt;theme&lt;/code&gt;. It now accepts &lt;code&gt;light&lt;/code&gt;, &lt;code&gt;dark&lt;/code&gt; or &lt;code&gt;auto&lt;/code&gt;, which sets the color scheme of the Connect pages.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed the default &lt;code&gt;scope&lt;/code&gt; of &lt;code&gt;generateAuthUrl()&lt;/code&gt;. It is now &lt;code&gt;read-write&lt;/code&gt;; it was &lt;code&gt;calendar&lt;/code&gt;, which is not a Connect scope. Connect treated it as &lt;code&gt;read-write&lt;/code&gt;, so the authorization behaves the same.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect .NET SDK 1.6.1</title><link>https://mobiscroll.com/releases/connect#dotnet-sdk-v1.6.1</link><guid isPermaLink="false">dotnet-sdk-1.6.1</guid><description>&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;Deliveries with a meeting on an event now verify.&lt;/p&gt;
&lt;h3&gt;Missing API features&lt;/h3&gt;
&lt;p&gt;Revoke, calendar &lt;code&gt;Account&lt;/code&gt; and &lt;code&gt;ReadOnly&lt;/code&gt;, meeting fields on event writes and the &lt;code&gt;Theme&lt;/code&gt; option are now covered.&lt;/p&gt;
&lt;h3&gt;Unknown providers&lt;/h3&gt;
&lt;p&gt;Responses from a newer Connect with a new calendar provider are read instead of rejected.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;Account&lt;/code&gt; and &lt;code&gt;ReadOnly&lt;/code&gt; to &lt;code&gt;Calendar&lt;/code&gt; objects. The API returns both for every calendar.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;Conference&lt;/code&gt; and &lt;code&gt;ConferenceData&lt;/code&gt; to &lt;code&gt;EventCreateData&lt;/code&gt; and &lt;code&gt;EventUpdateData&lt;/code&gt;. &lt;code&gt;AutoGenerate = true&lt;/code&gt; creates a meeting link.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed a &lt;code&gt;provider&lt;/code&gt; value this SDK version does not know, sent by a newer Connect, failing the whole &lt;code&gt;Events.ListAsync()&lt;/code&gt; response or &lt;code&gt;VerifyWebhookAsync()&lt;/code&gt; delivery. It is now read as the new &lt;code&gt;Provider.Unknown&lt;/code&gt;.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;VerifyWebhookAsync()&lt;/code&gt; rejecting every delivery whose events include a conference, with reason &lt;code&gt;InvalidPayload&lt;/code&gt;, because a delivery carries &lt;code&gt;conference&lt;/code&gt; as an object. Those deliveries now verify: &lt;code&gt;Conference&lt;/code&gt; is the join URL of that object, and &lt;code&gt;ConferenceData&lt;/code&gt; is the delivery&amp;rsquo;s &lt;code&gt;conferenceData&lt;/code&gt;, or one built from the object when the delivery has none.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;Auth.RevokeAsync()&lt;/code&gt;, which revokes every access and refresh token of the user through &lt;code&gt;POST /api/oauth/revoke&lt;/code&gt;. See &lt;a href=&quot;/docs/connect/api/oauth#endpoint-revoke&quot;&gt;Revoke Token&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;AuthorizeParams&lt;/code&gt; not accepting a theme. &lt;code&gt;AuthorizeParams.Theme&lt;/code&gt; now accepts &lt;code&gt;light&lt;/code&gt;, &lt;code&gt;dark&lt;/code&gt; or &lt;code&gt;auto&lt;/code&gt;, which sets the color scheme of the Connect pages.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Python SDK 1.6.1</title><link>https://mobiscroll.com/releases/connect#python-sdk-v1.6.1</link><guid isPermaLink="false">python-sdk-1.6.1</guid><description>&lt;h3&gt;Event writes&lt;/h3&gt;
&lt;p&gt;Creating and updating an event returns the event instead of raising an error.&lt;/p&gt;
&lt;h3&gt;Missing API features&lt;/h3&gt;
&lt;p&gt;Revoke, calendar &lt;code&gt;account&lt;/code&gt; and &lt;code&gt;read_only&lt;/code&gt;, meeting fields on event writes and the &lt;code&gt;theme&lt;/code&gt; option are now covered.&lt;/p&gt;
&lt;h3&gt;Webhook types&lt;/h3&gt;
&lt;p&gt;The webhook conference is annotated as the object a delivery carries.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;account&lt;/code&gt; and &lt;code&gt;read_only&lt;/code&gt; to &lt;code&gt;Calendar&lt;/code&gt; objects. The API returns both for every calendar.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;conference_data&lt;/code&gt; key to &lt;code&gt;events.create()&lt;/code&gt; and &lt;code&gt;events.update()&lt;/code&gt;, which send it as &lt;code&gt;conferenceData&lt;/code&gt;, so &lt;code&gt;{&quot;autoGenerate&quot;: True}&lt;/code&gt; creates a meeting link. &lt;code&gt;conference&lt;/code&gt; takes a meeting URL.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;events.create()&lt;/code&gt; and &lt;code&gt;events.update()&lt;/code&gt; raising &lt;code&gt;ServerError&lt;/code&gt; on every successful write, on the sync and async clients. They now return the written event.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed the annotation of &lt;code&gt;WebhookEvent.conference&lt;/code&gt;, which was &lt;code&gt;str | None&lt;/code&gt;. It is now &lt;code&gt;Mapping[str, Any] | None&lt;/code&gt;, the dict a &lt;code&gt;verify_webhook()&lt;/code&gt; delivery carries, with &lt;code&gt;url&lt;/code&gt;, &lt;code&gt;provider&lt;/code&gt;, &lt;code&gt;meetingProvider&lt;/code&gt; and &lt;code&gt;data&lt;/code&gt;.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;auth.revoke()&lt;/code&gt;, on the sync and async clients, which revokes every access and refresh token of the user through &lt;code&gt;POST /api/oauth/revoke&lt;/code&gt;. See &lt;a href=&quot;/docs/connect/api/oauth#endpoint-revoke&quot;&gt;Revoke Token&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;generate_auth_url()&lt;/code&gt; not accepting &lt;code&gt;theme&lt;/code&gt;, on the sync and async clients. It now accepts &lt;code&gt;light&lt;/code&gt;, &lt;code&gt;dark&lt;/code&gt; or &lt;code&gt;auto&lt;/code&gt;, which sets the color scheme of the Connect pages.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed the default &lt;code&gt;scope&lt;/code&gt; of &lt;code&gt;generate_auth_url()&lt;/code&gt;, on the sync and async clients. It is now &lt;code&gt;read-write&lt;/code&gt;; it was &lt;code&gt;calendar&lt;/code&gt;, which is not a Connect scope. Connect treated it as &lt;code&gt;read-write&lt;/code&gt;, so the authorization behaves the same.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Java SDK 1.6.1</title><link>https://mobiscroll.com/releases/connect#java-sdk-v1.6.1</link><guid isPermaLink="false">java-sdk-1.6.1</guid><description>&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;Deliveries with a meeting on an event now verify.&lt;/p&gt;
&lt;h3&gt;Missing API features&lt;/h3&gt;
&lt;p&gt;Revoke, calendar &lt;code&gt;getAccount()&lt;/code&gt; and &lt;code&gt;getReadOnly()&lt;/code&gt;, meeting fields on event writes and the &lt;code&gt;theme&lt;/code&gt; option are now covered.&lt;/p&gt;
&lt;h3&gt;Unknown providers&lt;/h3&gt;
&lt;p&gt;Responses from a newer Connect with a new calendar provider are read instead of rejected.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;getAccount()&lt;/code&gt; and &lt;code&gt;getReadOnly()&lt;/code&gt; to &lt;code&gt;Calendar&lt;/code&gt; objects. The API returns both for every calendar.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;conference()&lt;/code&gt; and &lt;code&gt;conferenceData()&lt;/code&gt; to the &lt;code&gt;EventCreateData&lt;/code&gt; and &lt;code&gt;EventUpdateData&lt;/code&gt; builders. &lt;code&gt;autoGenerate(true)&lt;/code&gt; creates a meeting link.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed a &lt;code&gt;provider&lt;/code&gt; value this SDK version does not know, sent by a newer Connect, failing the whole &lt;code&gt;events().list()&lt;/code&gt; response or &lt;code&gt;verifyWebhook()&lt;/code&gt; delivery. &lt;code&gt;getProvider()&lt;/code&gt; now returns &lt;code&gt;null&lt;/code&gt; for it; &lt;code&gt;Provider.fromWire()&lt;/code&gt; throws for it.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;verifyWebhook()&lt;/code&gt; rejecting every delivery whose events include a conference, with reason &lt;code&gt;INVALID_PAYLOAD&lt;/code&gt;, because a delivery carries &lt;code&gt;conference&lt;/code&gt; as an object. Those deliveries now verify: &lt;code&gt;getConference()&lt;/code&gt; is the join URL of that object, and &lt;code&gt;getConferenceData()&lt;/code&gt; is the delivery&amp;rsquo;s &lt;code&gt;conferenceData&lt;/code&gt;, or one built from the object when the delivery has none.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;auth().revoke()&lt;/code&gt;, which revokes every access and refresh token of the user through &lt;code&gt;POST /api/oauth/revoke&lt;/code&gt;. See &lt;a href=&quot;/docs/connect/api/oauth#endpoint-revoke&quot;&gt;Revoke Token&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;AuthUrlParams&lt;/code&gt; not accepting a theme. &lt;code&gt;AuthUrlParams.builder().theme()&lt;/code&gt; now accepts &lt;code&gt;light&lt;/code&gt;, &lt;code&gt;dark&lt;/code&gt; or &lt;code&gt;auto&lt;/code&gt;, which sets the color scheme of the Connect pages.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Go SDK 1.6.1</title><link>https://mobiscroll.com/releases/connect#go-sdk-v1.6.1</link><guid isPermaLink="false">go-sdk-1.6.1</guid><description>&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;Deliveries with a meeting on an event now verify.&lt;/p&gt;
&lt;h3&gt;Missing API features&lt;/h3&gt;
&lt;p&gt;Revoke, calendar &lt;code&gt;Account&lt;/code&gt; and &lt;code&gt;ReadOnly&lt;/code&gt;, meeting fields on event writes and the &lt;code&gt;Theme&lt;/code&gt; option are now covered.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;Account&lt;/code&gt; and &lt;code&gt;ReadOnly&lt;/code&gt; to &lt;code&gt;Calendar&lt;/code&gt; objects. The API returns both for every calendar.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;Conference&lt;/code&gt; and &lt;code&gt;ConferenceData&lt;/code&gt; to &lt;code&gt;EventCreateData&lt;/code&gt; and &lt;code&gt;EventUpdateData&lt;/code&gt;. &lt;code&gt;AutoGenerate&lt;/code&gt; creates a meeting link.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;VerifyWebhook&lt;/code&gt; rejecting every delivery whose events include a conference, with reason &lt;code&gt;invalid_payload&lt;/code&gt;, because a delivery carries &lt;code&gt;conference&lt;/code&gt; as an object. Those deliveries now verify: &lt;code&gt;Conference&lt;/code&gt; is the join URL of that object, and &lt;code&gt;ConferenceData&lt;/code&gt; is the delivery&amp;rsquo;s &lt;code&gt;conferenceData&lt;/code&gt;, or one built from the object when the delivery has none.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;Auth().Revoke()&lt;/code&gt;, which revokes every access and refresh token of the user through &lt;code&gt;POST /api/oauth/revoke&lt;/code&gt;. See &lt;a href=&quot;/docs/connect/api/oauth#endpoint-revoke&quot;&gt;Revoke Token&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;AuthURLParams&lt;/code&gt; not accepting a theme. &lt;code&gt;AuthURLParams.Theme&lt;/code&gt; now accepts &lt;code&gt;light&lt;/code&gt;, &lt;code&gt;dark&lt;/code&gt; or &lt;code&gt;auto&lt;/code&gt;, which sets the color scheme of the Connect pages.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Ruby SDK 1.6.1</title><link>https://mobiscroll.com/releases/connect#ruby-sdk-v1.6.1</link><guid isPermaLink="false">ruby-sdk-1.6.1</guid><description>&lt;h3&gt;Event writes&lt;/h3&gt;
&lt;p&gt;Attendees are sent as email strings, and the API&amp;rsquo;s own field names are accepted.&lt;/p&gt;
&lt;h3&gt;Missing API features&lt;/h3&gt;
&lt;p&gt;Revoke, calendar &lt;code&gt;account&lt;/code&gt; and &lt;code&gt;read_only&lt;/code&gt;, meeting fields on event writes and the &lt;code&gt;theme&lt;/code&gt; option are now covered.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;account&lt;/code&gt; and &lt;code&gt;read_only&lt;/code&gt; to &lt;code&gt;Calendar&lt;/code&gt; objects. The API returns both for every calendar.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;events.create&lt;/code&gt; and &lt;code&gt;events.update&lt;/code&gt; leaving out &lt;code&gt;status&lt;/code&gt; and &lt;code&gt;conference_data:&lt;/code&gt;. They now send &lt;code&gt;status&lt;/code&gt;, and &lt;code&gt;conference_data:&lt;/code&gt; as &lt;code&gt;conferenceData&lt;/code&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;events.create&lt;/code&gt; and &lt;code&gt;events.update&lt;/code&gt; silently leaving out &lt;code&gt;conferenceData:&lt;/code&gt;, &lt;code&gt;allDay:&lt;/code&gt;, &lt;code&gt;recurringEventId:&lt;/code&gt; and &lt;code&gt;updateMode:&lt;/code&gt;, the API&amp;rsquo;s spelling of &lt;code&gt;conference_data:&lt;/code&gt;, &lt;code&gt;all_day:&lt;/code&gt;, &lt;code&gt;recurring_event_id:&lt;/code&gt; and &lt;code&gt;update_mode:&lt;/code&gt;. They now accept both spellings.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;events.create&lt;/code&gt; and &lt;code&gt;events.update&lt;/code&gt; sending attendees as objects. They now send email strings, as the API expects.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;events.create&lt;/code&gt; and &lt;code&gt;events.update&lt;/code&gt; sending &lt;code&gt;color&lt;/code&gt;, which the API does not accept on writes.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We added the missing &lt;code&gt;auth.revoke&lt;/code&gt;, which revokes every access and refresh token of the user through &lt;code&gt;POST /api/oauth/revoke&lt;/code&gt;. See &lt;a href=&quot;/docs/connect/api/oauth#endpoint-revoke&quot;&gt;Revoke Token&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed &lt;code&gt;generate_auth_url&lt;/code&gt; not accepting &lt;code&gt;theme:&lt;/code&gt;. It now accepts &lt;code&gt;light&lt;/code&gt;, &lt;code&gt;dark&lt;/code&gt; or &lt;code&gt;auto&lt;/code&gt;, which sets the color scheme of the Connect pages.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.6.0</title><link>https://mobiscroll.com/releases/connect#api-v1.6.0</link><guid isPermaLink="false">1.6.0</guid><description>&lt;p&gt;This release changes how Connect delivers webhooks and how it handles token refreshes that come from more than one process.&lt;/p&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;p&gt;Each delivery now carries a signature that identifies the sender, and a failed delivery is attempted again over the following day. URLs that redirect are no longer followed.&lt;/p&gt;
&lt;h3&gt;Concurrent token refreshes&lt;/h3&gt;
&lt;p&gt;Processes sharing one login can refresh at once. They need to work from the same current token, because an outdated copy now ends the user&amp;rsquo;s connection.&lt;/p&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; We now sign every webhook delivery, so your endpoint can confirm that a request came from Mobiscroll Connect and was not altered on the way.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; We now retry a failed webhook delivery, up to 8 attempts over about 27 hours. A delivery is retried when your endpoint times out, cannot be reached, or answers &lt;code&gt;5xx&lt;/code&gt;, &lt;code&gt;408&lt;/code&gt; or &lt;code&gt;429&lt;/code&gt;. Any other &lt;code&gt;4xx&lt;/code&gt;, and any &lt;code&gt;3xx&lt;/code&gt;, is not retried. Every attempt at one delivery carries the same &lt;code&gt;webhook-id&lt;/code&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Connect no longer follows redirects from your webhook URL. A &lt;code&gt;3xx&lt;/code&gt; response counts as a failed delivery, so a URL that redirects, for example from &lt;code&gt;http://&lt;/code&gt; to &lt;code&gt;https://&lt;/code&gt;, needs to be set to its final address.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Several processes can now refresh the same token at the same time. A refresh token keeps working for 30 seconds after it is replaced, so every one of those requests succeeds and any of the refresh tokens they return can be stored.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; A refresh token that has been replaced more than once is now treated as reused: Connect revokes the authorization and its access tokens, and the user has to reconnect. Store the refresh token where all your processes share it, and read the current one before refreshing.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Every account in &lt;code&gt;GET /api/oauth/connection-status&lt;/code&gt; also carries &lt;code&gt;syncState&lt;/code&gt; and &lt;code&gt;syncStateUpdatedAt&lt;/code&gt;. &lt;code&gt;syncState&lt;/code&gt; reads &lt;code&gt;reauth_required&lt;/code&gt; once Google or Outlook has rejected the stored credentials, and the user has to reconnect before their calendars sync again. See &lt;a href=&quot;/docs/connect/core-concepts/scopes#connection-status&quot;&gt;Connection health&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Node.js SDK 1.6.0</title><link>https://mobiscroll.com/releases/connect#nodejs-sdk-v1.6.0</link><guid isPermaLink="false">nodejs-sdk-1.6.0</guid><description>&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;This release adds a method that verifies the signature of a webhook delivery in one call. Signed deliveries start with Connect API 1.6.0.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;verifyWebhook&lt;/code&gt; on &lt;code&gt;webhooks&lt;/code&gt;. It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or throws &lt;code&gt;WebhookVerificationError&lt;/code&gt; with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. See &lt;a href=&quot;/docs/connect/integration/node-sdk#webhooks-verify-webhook&quot;&gt;verifyWebhook&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect PHP SDK 1.6.0</title><link>https://mobiscroll.com/releases/connect#php-sdk-v1.6.0</link><guid isPermaLink="false">php-sdk-1.6.0</guid><description>&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;This release adds a method that verifies the signature of a webhook delivery in one call. Signed deliveries start with Connect API 1.6.0.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;verifyWebhook&lt;/code&gt; on &lt;code&gt;webhooks()&lt;/code&gt;. It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or throws &lt;code&gt;WebhookVerificationError&lt;/code&gt; with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. Requires the &lt;code&gt;sodium&lt;/code&gt; PHP extension and adds &lt;code&gt;psr/simple-cache&lt;/code&gt;. Under PHP-FPM, pass a PSR-16 cache in &lt;code&gt;webhookKeyCache&lt;/code&gt; so the keys are not fetched on every request. See &lt;a href=&quot;/docs/connect/integration/php-sdk#webhooks-verify-webhook&quot;&gt;verifyWebhook&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect .NET SDK 1.6.0</title><link>https://mobiscroll.com/releases/connect#dotnet-sdk-v1.6.0</link><guid isPermaLink="false">dotnet-sdk-1.6.0</guid><description>&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;This release adds a method that verifies the signature of a webhook delivery in one call. Signed deliveries start with Connect API 1.6.0.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;VerifyWebhookAsync&lt;/code&gt; on &lt;code&gt;Webhooks&lt;/code&gt;. It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or throws &lt;code&gt;WebhookVerificationException&lt;/code&gt; with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. Adds a dependency on the &lt;code&gt;NSec.Cryptography&lt;/code&gt; package. See &lt;a href=&quot;/docs/connect/integration/dotnet-sdk#webhooks-verify-webhook&quot;&gt;VerifyWebhookAsync&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Python SDK 1.6.0</title><link>https://mobiscroll.com/releases/connect#python-sdk-v1.6.0</link><guid isPermaLink="false">python-sdk-1.6.0</guid><description>&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;This release adds a method that verifies the signature of a webhook delivery in one call. Signed deliveries start with Connect API 1.6.0.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;verify_webhook&lt;/code&gt; on &lt;code&gt;webhooks&lt;/code&gt; (sync and async clients). It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or raises &lt;code&gt;WebhookVerificationError&lt;/code&gt; with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. Adds a dependency on the &lt;code&gt;cryptography&lt;/code&gt; package. See &lt;a href=&quot;/docs/connect/integration/python-sdk#webhooks-verify-webhook&quot;&gt;verify_webhook&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Java SDK 1.6.0</title><link>https://mobiscroll.com/releases/connect#java-sdk-v1.6.0</link><guid isPermaLink="false">java-sdk-1.6.0</guid><description>&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;This release adds a method that verifies the signature of a webhook delivery in one call. Signed deliveries start with Connect API 1.6.0.&lt;/p&gt;
&lt;h3&gt;Java 17&lt;/h3&gt;
&lt;p&gt;The minimum supported Java version is now 17.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;verifyWebhook&lt;/code&gt; on &lt;code&gt;webhooks()&lt;/code&gt;. It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or throws &lt;code&gt;WebhookVerificationException&lt;/code&gt; with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. This release requires Java 17 or later (previously 11). See &lt;a href=&quot;/docs/connect/integration/java-sdk#webhooks-verify-webhook&quot;&gt;verifyWebhook&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Go SDK 1.6.0</title><link>https://mobiscroll.com/releases/connect#go-sdk-v1.6.0</link><guid isPermaLink="false">go-sdk-1.6.0</guid><description>&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;This release adds a method that verifies the signature of a webhook delivery in one call. Signed deliveries start with Connect API 1.6.0.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;VerifyWebhook&lt;/code&gt; on &lt;code&gt;Webhooks()&lt;/code&gt;. It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or a &lt;code&gt;*WebhookVerificationError&lt;/code&gt; with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. See &lt;a href=&quot;/docs/connect/integration/go-sdk#webhooks-verify-webhook&quot;&gt;VerifyWebhook&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Ruby SDK 1.6.0</title><link>https://mobiscroll.com/releases/connect#ruby-sdk-v1.6.0</link><guid isPermaLink="false">ruby-sdk-1.6.0</guid><description>&lt;h3&gt;Webhook verification&lt;/h3&gt;
&lt;p&gt;This release adds a method that verifies the signature of a webhook delivery in one call. Signed deliveries start with Connect API 1.6.0.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;verify_webhook&lt;/code&gt; on &lt;code&gt;webhooks&lt;/code&gt;. It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or raises &lt;code&gt;WebhookVerificationError&lt;/code&gt; with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. See &lt;a href=&quot;/docs/connect/integration/ruby-sdk#webhooks-verify-webhook&quot;&gt;verify_webhook&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.5.3</title><link>https://mobiscroll.com/releases/connect#api-v1.5.3</link><guid isPermaLink="false">1.5.3</guid><description>&lt;p&gt;This release contains fixes, with a focus on users who connect several accounts, calendar details, and webhook reliability.&lt;/p&gt;
&lt;h3&gt;Multi-Account Fixes&lt;/h3&gt;
&lt;p&gt;For users who connected more than one account on the same provider, Connect treated the first account as the only one. Writes and webhooks now work on every account, and calendar filters return only what was requested. Integrations where each user connects a single account were not affected.&lt;/p&gt;
&lt;h3&gt;Calendar Ownership&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;GET /calendars&lt;/code&gt; now tells you which account owns each calendar and whether it can be written to.&lt;/p&gt;
&lt;h3&gt;Webhook Reliability&lt;/h3&gt;
&lt;p&gt;Google and Outlook channels keep running without intervention, and CalDAV delivery needs no separate setup.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; We added the &lt;code&gt;account&lt;/code&gt; and &lt;code&gt;readOnly&lt;/code&gt; fields to every calendar returned by &lt;code&gt;GET /calendars&lt;/code&gt;, on all four providers.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed an issue where &lt;code&gt;POST&lt;/code&gt;, &lt;code&gt;PUT&lt;/code&gt; and &lt;code&gt;DELETE /event&lt;/code&gt; returned &lt;code&gt;400&lt;/code&gt; for a calendar belonging to any Google account other than the first one the user connected.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed an issue on iCloud where updating an event previously created through Connect could make it appear as two separate events in the end user&amp;rsquo;s calendar app.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed the &lt;code&gt;calendarIds&lt;/code&gt; filter of &lt;code&gt;GET /events&lt;/code&gt; for users with several accounts on one provider. It could return events from every calendar on an account that owned none of the requested ids, instead of returning none.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed an issue where all-day events on iCloud and CalDAV calendars could come back from &lt;code&gt;GET /events&lt;/code&gt; dated one day earlier than the calendar shows.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed an issue on iCloud and CalDAV calendars where &lt;code&gt;GET /events&lt;/code&gt; could return &lt;code&gt;link&lt;/code&gt; as &lt;code&gt;{ params, val }&lt;/code&gt; instead of a URL string.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed an issue where a webhook subscription could not be created for those same Google calendars, so their changes never reached your webhook.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed webhook delivery for CalDAV calendars, which did not start on its own when a calendar was linked: notifications only arrived after separately calling &lt;code&gt;subscribe-webhook&lt;/code&gt;. Delivery now starts automatically, matching Google, Outlook and iCloud.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed an issue where webhook delivery on Google and Outlook calendars could stop silently once a channel expired. Channels are now renewed automatically before that happens.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; We fixed an issue where a user returning after their session expired landed on the provider-selection screen with no explanation. They now see a &amp;ldquo;Session Expired&amp;rdquo; message.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;General&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; We updated the API rate limits to 50 requests per second and 500 per minute, replacing the previous flat limit of 100 per 5 minutes.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Node.js SDK 1.5.1</title><link>https://mobiscroll.com/releases/connect#nodejs-sdk-v1.5.1</link><guid isPermaLink="false">nodejs-sdk-1.5.1</guid><description>&lt;h3&gt;Package metadata&lt;/h3&gt;
&lt;p&gt;A metadata-only release. The npm listing now carries a description of what the SDK does, keywords, and links to the product page, the source and the issue tracker. The package code and public API are unchanged, so there is nothing to do beyond upgrading if you want the current version.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Package metadata only &amp;mdash; the npm listing now carries a description of what the SDK does, keywords, and links to the product page, the source and the issue tracker. No code or public API changes.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Node.js SDK 1.5.0</title><link>https://mobiscroll.com/releases/connect#nodejs-sdk-v1.5.0</link><guid isPermaLink="false">nodejs-sdk-1.5.0</guid><description>&lt;h3&gt;Webhook subscription management&lt;/h3&gt;
&lt;p&gt;The SDK now wraps the API&amp;rsquo;s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;subscribeWebhook&lt;/code&gt; and &lt;code&gt;unsubscribeWebhook&lt;/code&gt; on &lt;code&gt;webhooks&lt;/code&gt;, wrapping the API&amp;rsquo;s &lt;code&gt;POST /subscribe-webhook&lt;/code&gt; and &lt;code&gt;POST /unsubscribe-webhook&lt;/code&gt; endpoints &amp;mdash; previously only reachable with a raw HTTP call.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect PHP SDK 1.5.1</title><link>https://mobiscroll.com/releases/connect#php-sdk-v1.5.1</link><guid isPermaLink="false">php-sdk-1.5.1</guid><description>&lt;h3&gt;Package metadata&lt;/h3&gt;
&lt;p&gt;A metadata-only release. The Packagist listing now carries a description of what the SDK does, keywords, and links to the product page, the source and the issue tracker. The package code and public API are unchanged, so there is nothing to do beyond upgrading if you want the current version.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Package metadata only &amp;mdash; the Packagist listing now carries a description of what the SDK does, keywords, and links to the product page, the source and the issue tracker. No code or public API changes.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect PHP SDK 1.5.0</title><link>https://mobiscroll.com/releases/connect#php-sdk-v1.5.0</link><guid isPermaLink="false">php-sdk-1.5.0</guid><description>&lt;h3&gt;Webhook subscription management&lt;/h3&gt;
&lt;p&gt;The SDK now wraps the API&amp;rsquo;s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;subscribeWebhook&lt;/code&gt; and &lt;code&gt;unsubscribeWebhook&lt;/code&gt; on &lt;code&gt;webhooks&lt;/code&gt;, wrapping the API&amp;rsquo;s &lt;code&gt;POST /subscribe-webhook&lt;/code&gt; and &lt;code&gt;POST /unsubscribe-webhook&lt;/code&gt; endpoints &amp;mdash; previously only reachable with a raw HTTP call.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect .NET SDK 1.5.1</title><link>https://mobiscroll.com/releases/connect#dotnet-sdk-v1.5.1</link><guid isPermaLink="false">dotnet-sdk-1.5.1</guid><description>&lt;h3&gt;Package metadata&lt;/h3&gt;
&lt;p&gt;A metadata-only release. The NuGet listing now carries a description of what the SDK does, tags, and a project link alongside the repository link. The package code and public API are unchanged, so there is nothing to do beyond upgrading if you want the current version.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Package metadata only &amp;mdash; the NuGet listing now carries a description of what the SDK does, tags, and a project link alongside the repository link. No code or public API changes.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect .NET SDK 1.5.0</title><link>https://mobiscroll.com/releases/connect#dotnet-sdk-v1.5.0</link><guid isPermaLink="false">dotnet-sdk-1.5.0</guid><description>&lt;h3&gt;Webhook subscription management&lt;/h3&gt;
&lt;p&gt;The SDK now wraps the API&amp;rsquo;s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;SubscribeWebhookAsync&lt;/code&gt; and &lt;code&gt;UnsubscribeWebhookAsync&lt;/code&gt; on &lt;code&gt;Webhooks&lt;/code&gt;, wrapping the API&amp;rsquo;s &lt;code&gt;POST /subscribe-webhook&lt;/code&gt; and &lt;code&gt;POST /unsubscribe-webhook&lt;/code&gt; endpoints &amp;mdash; previously only reachable with a raw HTTP call.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Python SDK 1.5.1</title><link>https://mobiscroll.com/releases/connect#python-sdk-v1.5.1</link><guid isPermaLink="false">python-sdk-1.5.1</guid><description>&lt;h3&gt;Package metadata&lt;/h3&gt;
&lt;p&gt;A metadata-only release. The PyPI listing now carries a description of what the SDK does, keywords, and links to the issue tracker and changelog, and the package is marked production-ready rather than beta. The package code and public API are unchanged, so there is nothing to do beyond upgrading if you want the current version.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Package metadata only &amp;mdash; the PyPI listing now carries a description of what the SDK does, keywords, links to the issue tracker and changelog, and is marked production-ready rather than beta. No code or public API changes.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Python SDK 1.5.0</title><link>https://mobiscroll.com/releases/connect#python-sdk-v1.5.0</link><guid isPermaLink="false">python-sdk-1.5.0</guid><description>&lt;h3&gt;Webhook subscription management&lt;/h3&gt;
&lt;p&gt;The SDK now wraps the API&amp;rsquo;s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;subscribe_webhook&lt;/code&gt; and &lt;code&gt;unsubscribe_webhook&lt;/code&gt; on &lt;code&gt;webhooks&lt;/code&gt; (sync and async clients), wrapping the API&amp;rsquo;s &lt;code&gt;POST /subscribe-webhook&lt;/code&gt; and &lt;code&gt;POST /unsubscribe-webhook&lt;/code&gt; endpoints &amp;mdash; previously only reachable with a raw HTTP call.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Java SDK 1.5.1</title><link>https://mobiscroll.com/releases/connect#java-sdk-v1.5.1</link><guid isPermaLink="false">java-sdk-1.5.1</guid><description>&lt;h3&gt;Package metadata&lt;/h3&gt;
&lt;p&gt;A metadata-only release. The Maven Central listing now carries a description of what the SDK does, a project link that points at the product page rather than the repository, and an issue tracker link. The artifact code and public API are unchanged, so there is nothing to do beyond upgrading if you want the current version.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Package metadata only &amp;mdash; the Maven Central listing now carries a description of what the SDK does, a project link pointing at the product page rather than the repository, and an issue tracker link. No code or public API changes.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Java SDK 1.5.0</title><link>https://mobiscroll.com/releases/connect#java-sdk-v1.5.0</link><guid isPermaLink="false">java-sdk-1.5.0</guid><description>&lt;h3&gt;Webhook subscription management&lt;/h3&gt;
&lt;p&gt;The SDK now wraps the API&amp;rsquo;s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;subscribeWebhook&lt;/code&gt; and &lt;code&gt;unsubscribeWebhook&lt;/code&gt; on &lt;code&gt;webhooks&lt;/code&gt;, wrapping the API&amp;rsquo;s &lt;code&gt;POST /subscribe-webhook&lt;/code&gt; and &lt;code&gt;POST /unsubscribe-webhook&lt;/code&gt; endpoints &amp;mdash; previously only reachable with a raw HTTP call.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Go SDK 1.5.1</title><link>https://mobiscroll.com/releases/connect#go-sdk-v1.5.1</link><guid isPermaLink="false">go-sdk-1.5.1</guid><description>&lt;h3&gt;Package metadata&lt;/h3&gt;
&lt;p&gt;A metadata-only release. The package documentation on pkg.go.dev now opens by describing what the SDK does rather than how it relates to the other Connect SDKs. The module code and public API are unchanged, so there is nothing to do beyond upgrading if you want the current version.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Package metadata only &amp;mdash; the package documentation on pkg.go.dev now opens by describing what the SDK does rather than how it relates to the other Connect SDKs. No code or public API changes.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Go SDK 1.5.0</title><link>https://mobiscroll.com/releases/connect#go-sdk-v1.5.0</link><guid isPermaLink="false">go-sdk-1.5.0</guid><description>&lt;h3&gt;Webhook subscription management&lt;/h3&gt;
&lt;p&gt;The SDK now wraps the API&amp;rsquo;s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;SubscribeWebhook&lt;/code&gt; and &lt;code&gt;UnsubscribeWebhook&lt;/code&gt;, wrapping the API&amp;rsquo;s &lt;code&gt;POST /subscribe-webhook&lt;/code&gt; and &lt;code&gt;POST /unsubscribe-webhook&lt;/code&gt; endpoints &amp;mdash; previously only reachable with a raw HTTP call.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Ruby SDK 1.5.1</title><link>https://mobiscroll.com/releases/connect#ruby-sdk-v1.5.1</link><guid isPermaLink="false">ruby-sdk-1.5.1</guid><description>&lt;h3&gt;Package metadata&lt;/h3&gt;
&lt;p&gt;A metadata-only release. The RubyGems listing now carries a description of what the SDK does and links to the documentation and changelog. The gem code and public API are unchanged, so there is nothing to do beyond upgrading if you want the current version.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Package metadata only &amp;mdash; the RubyGems listing now carries a description of what the SDK does and links to the documentation and changelog. No code or public API changes.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Ruby SDK 1.5.0</title><link>https://mobiscroll.com/releases/connect#ruby-sdk-v1.5.0</link><guid isPermaLink="false">ruby-sdk-1.5.0</guid><description>&lt;h3&gt;Webhook subscription management&lt;/h3&gt;
&lt;p&gt;The SDK now wraps the API&amp;rsquo;s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The SDK now exposes &lt;code&gt;subscribe_webhook&lt;/code&gt; and &lt;code&gt;unsubscribe_webhook&lt;/code&gt; on &lt;code&gt;webhooks&lt;/code&gt;, wrapping the API&amp;rsquo;s &lt;code&gt;POST /subscribe-webhook&lt;/code&gt; and &lt;code&gt;POST /unsubscribe-webhook&lt;/code&gt; endpoints &amp;mdash; previously only reachable with a raw HTTP call.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.5.2</title><link>https://mobiscroll.com/releases/connect#api-v1.5.2</link><guid isPermaLink="false">1.5.2</guid><description>&lt;h3&gt;Event identifiers on iCloud calendars&lt;/h3&gt;
&lt;p&gt;A patch release for anyone writing events to iCloud or CalDAV calendars. Creating an event handed back one identifier while every other endpoint expected another, so an integration that saved it could not afterwards change or remove what it had made. Google and Outlook were never affected.&lt;/p&gt;
&lt;p&gt;Nothing has to change when you upgrade, because both identifiers are accepted from here on. The one thing worth reading in full is the note about trimming the identifier: that shortcut is now unnecessary on iCloud, and has always been wrong on other CalDAV servers.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; Creating an event on an iCloud calendar returned a different identifier than the update and delete endpoints expect, so an integration that saved it could not change or remove that event afterwards.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; Update and delete now accept both identifiers, so anything you stored before this release keeps working. If you worked around this by trimming &amp;ldquo;@mobiscroll.com&amp;rdquo; off the identifier, that is no longer necessary &amp;mdash; but never do it on CalDAV calendars, where the full value is the identifier.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; On iCloud and CalDAV calendars, update and delete could act on the wrong event, or fail to find one that was listed.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.5.1</title><link>https://mobiscroll.com/releases/connect#api-v1.5.1</link><guid isPermaLink="false">1.5.1</guid><description>&lt;h3&gt;37 languages on the Connect pages&lt;/h3&gt;
&lt;p&gt;Connect&amp;rsquo;s user-facing screens now cover the same languages as the Mobiscroll component library, up from eight. Twenty-nine were added in this release, so most users reaching your connection flow will see it in their own language without you changing anything.&lt;/p&gt;
&lt;p&gt;Two details are worth checking if you pass &lt;code&gt;?lng=&lt;/code&gt; explicitly. Chinese is now selected by &lt;strong&gt;script&lt;/strong&gt; &amp;mdash; &lt;code&gt;zh-Hans&lt;/code&gt; or &lt;code&gt;zh-Hant&lt;/code&gt; &amp;mdash; with the familiar region codes mapped onto them. Ukrainian is &lt;code&gt;uk&lt;/code&gt;, the language code, rather than the country code. Everything else continues to work as before: &lt;code&gt;?lng=&lt;/code&gt; wins, &lt;code&gt;Accept-Language&lt;/code&gt; decides otherwise, and API responses stay English.&lt;/p&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The Connect pages are now localized in &lt;strong&gt;37 languages&lt;/strong&gt;, matching the language set of the Mobiscroll component library. Newly added: Dutch, Polish, Czech, Slovak, Hungarian, Romanian, Croatian, Serbian, Bulgarian, Lithuanian, Catalan, Greek, Turkish, Swedish, Danish, Norwegian, Finnish, Russian, Ukrainian, Hindi, Thai, Vietnamese, Japanese, Korean, Simplified Chinese, Traditional Chinese, British English, Hebrew and Persian.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Hebrew (&lt;code&gt;he&lt;/code&gt;) and Persian (&lt;code&gt;fa&lt;/code&gt;) join Arabic as right-to-left languages; the Connect pages switch direction automatically when one of them is active.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Chinese is selected by script rather than region: &lt;code&gt;?lng=zh-Hans&lt;/code&gt; for Simplified and &lt;code&gt;?lng=zh-Hant&lt;/code&gt; for Traditional. &lt;code&gt;zh-CN&lt;/code&gt;, &lt;code&gt;zh-SG&lt;/code&gt; and &lt;code&gt;zh-MY&lt;/code&gt; resolve to Simplified; &lt;code&gt;zh-TW&lt;/code&gt;, &lt;code&gt;zh-HK&lt;/code&gt; and &lt;code&gt;zh-MO&lt;/code&gt; to Traditional; a bare &lt;code&gt;zh&lt;/code&gt; to Simplified.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Ukrainian uses the ISO 639-1 language code &lt;code&gt;?lng=uk&lt;/code&gt;. The country code &lt;code&gt;ua&lt;/code&gt; is accepted as an alias, so either value works.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Languages are also matched under the codes browsers commonly send: &lt;code&gt;nb&lt;/code&gt; and &lt;code&gt;nb-NO&lt;/code&gt; for Norwegian, &lt;code&gt;iw&lt;/code&gt; for Hebrew, &lt;code&gt;ru-UA&lt;/code&gt; and &lt;code&gt;ru-BY&lt;/code&gt; for Russian, and &lt;code&gt;en-AU&lt;/code&gt;, &lt;code&gt;en-NZ&lt;/code&gt;, &lt;code&gt;en-IE&lt;/code&gt; and &lt;code&gt;en-ZA&lt;/code&gt; for British English. No change is needed for &lt;code&gt;Accept-Language&lt;/code&gt; to pick them up.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.5.0</title><link>https://mobiscroll.com/releases/connect#api-v1.5.0</link><guid isPermaLink="false">1.5.0</guid><description>&lt;h3&gt;Calendar access that was never granted&lt;/h3&gt;
&lt;p&gt;Google lets a user finish signing in while skipping the calendar checkbox, leaving a connection that reports success and no calendars. The flow now stops there and asks for what it needs.&lt;/p&gt;
&lt;p&gt;Read the second fix before you ship: it changes what an existing integration gets back in a case it previously handled silently. Nothing can be done server-side for the users already affected &amp;mdash; two new fields tell you which of them to send back through the flow.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; Where no connected account has calendar access, &lt;code&gt;GET /calendars&lt;/code&gt;, &lt;code&gt;GET /events&lt;/code&gt; and the &lt;code&gt;/event&lt;/code&gt; write endpoints now return &lt;code&gt;403&lt;/code&gt; with &lt;code&gt;code: &amp;quot;calendar_permission_required&amp;quot;&lt;/code&gt; and an &lt;code&gt;accounts&lt;/code&gt; array naming who must reconnect, instead of an empty list. A request that used to return an empty array can now be a &lt;code&gt;403&lt;/code&gt; &amp;mdash; only where the result was already unusable, since a user with no connected accounts still gets an empty list. If only some accounts withheld access the request still succeeds, with the skipped ones named in the &lt;code&gt;X-Connect-Calendar-Permission-Missing&lt;/code&gt; header.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Every account in &lt;code&gt;GET /api/oauth/connection-status&lt;/code&gt; now carries &lt;code&gt;grantedScopes&lt;/code&gt; and &lt;code&gt;calendarPermissionGranted&lt;/code&gt;. The flag is evaluated against the calling request&amp;rsquo;s scope, so a grant sufficient for &lt;code&gt;free-busy&lt;/code&gt; can still be &lt;code&gt;false&lt;/code&gt; for &lt;code&gt;read-write&lt;/code&gt;; it is &lt;code&gt;null&lt;/code&gt; for Apple and CalDAV, which have no permissions to withhold. Check it before showing a calendar picker &amp;mdash; see the &lt;a href=&quot;/docs/connect/scopes#partial-consent&quot;&gt;Scopes &amp;amp; Permissions&lt;/a&gt; docs page.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; Google shows the calendar permission as a separate checkbox. Leaving it unticked still produced a valid sign-in, so the account looked connected while &lt;code&gt;GET /calendars&lt;/code&gt; returned &lt;code&gt;[]&lt;/code&gt; for it. The Google flow now checks what was granted and asks the user for the permission instead of completing. Accounts already connected this way cannot be repaired &amp;mdash; providers only issue permissions at consent time, so those users must reconnect.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Node.js SDK 1.2.0</title><link>https://mobiscroll.com/releases/connect#nodejs-sdk-v1.2.0</link><guid isPermaLink="false">nodejs-sdk-1.2.0</guid><description>&lt;h3&gt;Calendar access that was never granted&lt;/h3&gt;
&lt;p&gt;A user can finish connecting a Google account without granting access to their calendar. The connection then looks healthy and returns nothing. This release makes that visible before you call, and turns the silent empty result into an error.&lt;/p&gt;
&lt;p&gt;Unrelated: the event model catches up with three fields it never mapped.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The event model now exposes &lt;code&gt;description&lt;/code&gt;, &lt;code&gt;conferenceData&lt;/code&gt; and &lt;code&gt;lastModified&lt;/code&gt;. The API has returned all three for some time; they were simply missing from the SDK, so reading them no longer means going through the raw response.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; A calendar or event call where no connected account has calendar access now raises &lt;code&gt;CalendarPermissionError&lt;/code&gt;, with an &lt;code&gt;accounts&lt;/code&gt; property. It subclasses &lt;code&gt;AuthenticationError&lt;/code&gt;, so existing handlers keep working while new code can read which accounts must reconnect.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; &lt;code&gt;ConnectedAccount&lt;/code&gt; gained &lt;code&gt;grantedScopes&lt;/code&gt; and &lt;code&gt;calendarPermissionGranted&lt;/code&gt;, so &lt;code&gt;getConnectionStatus&lt;/code&gt; reports which connected accounts withheld calendar access and cannot list calendars.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect PHP SDK 1.2.0</title><link>https://mobiscroll.com/releases/connect#php-sdk-v1.2.0</link><guid isPermaLink="false">php-sdk-1.2.0</guid><description>&lt;h3&gt;Calendar access that was never granted&lt;/h3&gt;
&lt;p&gt;A user can finish connecting a Google account without granting access to their calendar. The connection then looks healthy and returns nothing. This release makes that visible before you call, and turns the silent empty result into an error.&lt;/p&gt;
&lt;p&gt;Unrelated: the event model catches up with three fields it never mapped.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The event model now exposes &lt;code&gt;description&lt;/code&gt;, &lt;code&gt;conferenceData&lt;/code&gt; and &lt;code&gt;lastModified&lt;/code&gt;. The API has returned all three for some time; they were simply missing from the SDK, so reading them no longer means going through the raw response.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; A calendar or event call where no connected account has calendar access now raises &lt;code&gt;CalendarPermissionError&lt;/code&gt;, with &lt;code&gt;getAccounts()&lt;/code&gt;. It extends &lt;code&gt;AuthenticationError&lt;/code&gt;, so existing handlers keep working while new code can read which accounts must reconnect.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Each account returned by &lt;code&gt;getConnectionStatus&lt;/code&gt; now carries &lt;code&gt;grantedScopes&lt;/code&gt; and &lt;code&gt;calendarPermissionGranted&lt;/code&gt;, reporting which connected accounts withheld calendar access and cannot list calendars.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect .NET SDK 1.2.0</title><link>https://mobiscroll.com/releases/connect#dotnet-sdk-v1.2.0</link><guid isPermaLink="false">dotnet-sdk-1.2.0</guid><description>&lt;h3&gt;Calendar access that was never granted&lt;/h3&gt;
&lt;p&gt;A user can finish connecting a Google account without granting access to their calendar. The connection then looks healthy and returns nothing. This release makes that visible before you call, and turns the silent empty result into an error.&lt;/p&gt;
&lt;p&gt;Unrelated: the event model catches up with three fields it never mapped.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The event model now exposes &lt;code&gt;Description&lt;/code&gt;, &lt;code&gt;ConferenceData&lt;/code&gt; and &lt;code&gt;LastModified&lt;/code&gt;. The API has returned all three for some time; they were simply missing from the SDK, so reading them no longer means going through the raw response.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; A calendar or event call where no connected account has calendar access now raises &lt;code&gt;CalendarPermissionException&lt;/code&gt;, with an &lt;code&gt;Accounts&lt;/code&gt; property. It derives from &lt;code&gt;AuthenticationException&lt;/code&gt;, so existing handlers keep working while new code can read which accounts must reconnect.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; &lt;code&gt;ConnectedAccount&lt;/code&gt; gained &lt;code&gt;GrantedScopes&lt;/code&gt; and &lt;code&gt;CalendarPermissionGranted&lt;/code&gt;, so &lt;code&gt;GetConnectionStatusAsync&lt;/code&gt; reports which connected accounts withheld calendar access and cannot list calendars.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Python SDK 1.2.0</title><link>https://mobiscroll.com/releases/connect#python-sdk-v1.2.0</link><guid isPermaLink="false">python-sdk-1.2.0</guid><description>&lt;h3&gt;Calendar access that was never granted&lt;/h3&gt;
&lt;p&gt;A user can finish connecting a Google account without granting access to their calendar. The connection then looks healthy and returns nothing. This release makes that visible before you call, and turns the silent empty result into an error.&lt;/p&gt;
&lt;p&gt;Unrelated: the event model catches up with three fields it never mapped.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The event model now exposes &lt;code&gt;description&lt;/code&gt;, &lt;code&gt;conference_data&lt;/code&gt; and &lt;code&gt;last_modified&lt;/code&gt;. The API has returned all three for some time; they were simply missing from the SDK, so reading them no longer means going through the raw response.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; A calendar or event call where no connected account has calendar access now raises &lt;code&gt;CalendarPermissionError&lt;/code&gt;, with an &lt;code&gt;accounts&lt;/code&gt; attribute. It subclasses &lt;code&gt;AuthenticationError&lt;/code&gt;, so existing handlers keep working while new code can read which accounts must reconnect.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; &lt;code&gt;ConnectedAccount&lt;/code&gt; gained &lt;code&gt;granted_scopes&lt;/code&gt; and &lt;code&gt;calendar_permission_granted&lt;/code&gt;, so &lt;code&gt;get_connection_status&lt;/code&gt; reports which connected accounts withheld calendar access and cannot list calendars.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Java SDK 1.2.0</title><link>https://mobiscroll.com/releases/connect#java-sdk-v1.2.0</link><guid isPermaLink="false">java-sdk-1.2.0</guid><description>&lt;h3&gt;Calendar access that was never granted&lt;/h3&gt;
&lt;p&gt;A user can finish connecting a Google account without granting access to their calendar. The connection then looks healthy and returns nothing. This release makes that visible before you call, and turns the silent empty result into an error.&lt;/p&gt;
&lt;p&gt;Unrelated: the event model catches up with three fields it never mapped.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The event model now exposes &lt;code&gt;getDescription()&lt;/code&gt;, &lt;code&gt;getConferenceData()&lt;/code&gt; and &lt;code&gt;getLastModified()&lt;/code&gt;. The API has returned all three for some time; they were simply missing from the SDK, so reading them no longer means going through the raw response.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; A calendar or event call where no connected account has calendar access now raises &lt;code&gt;CalendarPermissionException&lt;/code&gt;, with &lt;code&gt;getAccounts()&lt;/code&gt;. It extends &lt;code&gt;AuthenticationException&lt;/code&gt;, so existing handlers keep working while new code can read which accounts must reconnect.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; &lt;code&gt;ConnectedAccount&lt;/code&gt; gained &lt;code&gt;getGrantedScopes()&lt;/code&gt; and &lt;code&gt;getCalendarPermissionGranted()&lt;/code&gt;, so &lt;code&gt;getConnectionStatus&lt;/code&gt; reports which connected accounts withheld calendar access and cannot list calendars.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Go SDK 1.2.0</title><link>https://mobiscroll.com/releases/connect#go-sdk-v1.2.0</link><guid isPermaLink="false">go-sdk-1.2.0</guid><description>&lt;h3&gt;Calendar access that was never granted&lt;/h3&gt;
&lt;p&gt;A user can finish connecting a Google account without granting access to their calendar. The connection then looks healthy and returns nothing. This release makes that visible before you call, and turns the silent empty result into an error.&lt;/p&gt;
&lt;p&gt;Unrelated: the event model catches up with three fields it never mapped.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The event model now exposes &lt;code&gt;Description&lt;/code&gt;, &lt;code&gt;ConferenceData&lt;/code&gt; and &lt;code&gt;LastModified&lt;/code&gt;. The API has returned all three for some time; they were simply missing from the SDK, so reading them no longer means going through the raw response.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; A calendar or event call where no connected account has calendar access now raises &lt;code&gt;*CalendarPermissionError&lt;/code&gt;, with an &lt;code&gt;Accounts&lt;/code&gt; field. It unwraps to &lt;code&gt;*AuthenticationError&lt;/code&gt;, so existing handlers keep working while new code can read which accounts must reconnect.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; &lt;code&gt;ConnectedAccount&lt;/code&gt; gained &lt;code&gt;GrantedScopes&lt;/code&gt; and &lt;code&gt;CalendarPermissionGranted&lt;/code&gt;, so &lt;code&gt;GetConnectionStatus&lt;/code&gt; reports which connected accounts withheld calendar access and cannot list calendars.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Ruby SDK 1.2.0</title><link>https://mobiscroll.com/releases/connect#ruby-sdk-v1.2.0</link><guid isPermaLink="false">ruby-sdk-1.2.0</guid><description>&lt;h3&gt;Calendar access that was never granted&lt;/h3&gt;
&lt;p&gt;A user can finish connecting a Google account without granting access to their calendar. The connection then looks healthy and returns nothing. This release makes that visible before you call, and turns the silent empty result into an error.&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; A calendar or event call where no connected account has calendar access now raises &lt;code&gt;CalendarPermissionError&lt;/code&gt;, with an &lt;code&gt;accounts&lt;/code&gt; reader. It subclasses &lt;code&gt;AuthenticationError&lt;/code&gt;, so existing handlers keep working while new code can read which accounts must reconnect.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; &lt;code&gt;ConnectedAccount&lt;/code&gt; gained &lt;code&gt;granted_scopes&lt;/code&gt; and &lt;code&gt;calendar_permission_granted&lt;/code&gt;, so &lt;code&gt;get_connection_status&lt;/code&gt; reports which connected accounts withheld calendar access and cannot list calendars.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.4.1</title><link>https://mobiscroll.com/releases/connect#api-v1.4.1</link><guid isPermaLink="false">1.4.1</guid><description>&lt;h3&gt;Microsoft webhook payloads and echo filtering&lt;/h3&gt;
&lt;p&gt;Two defects compounded each other on Microsoft calendars: deliveries arrived stripped of the data you attached to the event, and changes your own application made through the API came back to you as notifications. Google was never affected, so an integration that behaved correctly there could still break on Outlook.&lt;/p&gt;
&lt;p&gt;Read the second fix before touching your handler &amp;mdash; it changes what you receive. A create, update or delete you perform through the API now produces no callback at all, where previously at least one arrived. Filtering happens per server instance, so keep an origin marker in &lt;code&gt;custom&lt;/code&gt; as a second line of defence; on Microsoft it finally survives the round trip.&lt;/p&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; Webhook deliveries for Microsoft (Outlook) events now include &lt;code&gt;custom&lt;/code&gt;, matching what &lt;code&gt;GET /events&lt;/code&gt; returns for the same event. Microsoft rows previously arrived without it, and without &lt;code&gt;original.extensions&lt;/code&gt;, so an origin marker such as &lt;code&gt;custom.source = &amp;quot;my-system&amp;quot;&lt;/code&gt; never reached your endpoint. Google was unaffected.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; Webhook echoes of your own &lt;code&gt;POST /event&lt;/code&gt;, &lt;code&gt;PUT /event&lt;/code&gt; and &lt;code&gt;DELETE /event&lt;/code&gt; calls are now suppressed for the full 30-second window, including notifications that arrive before the API call returns. Only the first echo used to be filtered, and one Microsoft write raises several notifications, so at least one always reached your endpoint.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.4.0</title><link>https://mobiscroll.com/releases/connect#api-v1.4.0</link><guid isPermaLink="false">1.4.0</guid><description>&lt;h3&gt;Application verification&lt;/h3&gt;
&lt;p&gt;Mobiscroll can now review your application and mark it verified. This is our review, not the calendar providers&amp;rsquo; &amp;mdash; Mobiscroll owns the upstream Google and Microsoft OAuth applications, so you never run Google brand verification or a Microsoft publisher review yourself.&lt;/p&gt;
&lt;p&gt;An unverified application is not held back: it still shows its own branding and serves your users normally. Note that a logo needs the Scale plan or higher whatever the verification status, so on lower plans there is no logo for a reviewer to look at.&lt;/p&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; You can now have your application reviewed by Mobiscroll and marked as verified. Until it is, your users see a note on the authorization screen saying Mobiscroll has not reviewed the application; verifying removes it. Submit for review from the &lt;strong&gt;Verification&lt;/strong&gt; page of your application in the dashboard. Verification is optional and gates nothing &amp;mdash; it does not unlock features, change any plan limit, or affect the Connect API. See &lt;a href=&quot;/docs/connect/verification&quot;&gt;App Verification&lt;/a&gt; docs page for what a reviewer checks, the details you need to supply, and which changes send an application back for review.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.3.3</title><link>https://mobiscroll.com/releases/connect#api-v1.3.3</link><guid isPermaLink="false">1.3.3</guid><description>&lt;h3&gt;Correct Google attendee lists, and four new languages&lt;/h3&gt;
&lt;p&gt;A correctness fix for anyone reading Google events: &lt;code&gt;attendees&lt;/code&gt; now reports exactly the guests Google reports, with nothing synthesised on top. Read the first two fixes below before removing any client-side filtering you have in place &amp;mdash; one case still needs it.&lt;/p&gt;
&lt;p&gt;The Connect screens gain four languages for a total of eight, and &lt;code&gt;lng&lt;/code&gt; now takes region-qualified codes, which is what makes European and Brazilian Portuguese separately selectable. The languages that shipped earlier also received copy corrections.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; For a Google event whose organizer is a group calendar, that calendar&amp;rsquo;s address (ending in &lt;code&gt;@group.calendar.google.com&lt;/code&gt;) was added to &lt;code&gt;attendees&lt;/code&gt; with &lt;code&gt;&amp;quot;status&amp;quot;: &amp;quot;accepted&amp;quot;&lt;/code&gt; even when Google did not list it as a guest &amp;mdash; a participant that was not on the event, marked as having accepted an invitation it never received. The &lt;code&gt;attendees&lt;/code&gt; list now mirrors the guest list Google returns: nothing is added and nothing is inferred. An organizer Google does list as a guest is still returned, flagged &lt;code&gt;&amp;quot;organizer&amp;quot;: true&lt;/code&gt;, including a group calendar&amp;rsquo;s own address. Those addresses are not mailboxes, so if you filter them out of a guest list or a mail fan-out, keep doing so.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; A Google event with no guests returned a one-entry &lt;code&gt;attendees&lt;/code&gt; list holding the organizer, instead of an empty list. Microsoft, iCloud, and CalDAV events are unaffected &amp;mdash; those protocols keep the organizer outside the guest list, so the organizer is still added there as an &lt;code&gt;&amp;quot;organizer&amp;quot;: true&lt;/code&gt; entry.&lt;/li&gt;&lt;/ul&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The Connect screens are now available in German (&lt;code&gt;de&lt;/code&gt;), Italian (&lt;code&gt;it&lt;/code&gt;), European Portuguese (&lt;code&gt;pt-PT&lt;/code&gt;), and Brazilian Portuguese (&lt;code&gt;pt-BR&lt;/code&gt;), bringing the total to eight languages alongside English, Spanish, French, and Arabic. Select one with &lt;code&gt;?lng=&amp;lt;code&amp;gt;&lt;/code&gt; on the authorize URL, or let the browser &lt;code&gt;Accept-Language&lt;/code&gt; header pick it automatically.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; &lt;code&gt;lng&lt;/code&gt; now accepts region-qualified codes, so European and Brazilian Portuguese are separate languages. Codes are written with a hyphen, as in &lt;code&gt;pt-BR&lt;/code&gt;; matching is case-insensitive, and an underscore is accepted in place of the hyphen, so &lt;code&gt;pt-br&lt;/code&gt;, &lt;code&gt;PT-BR&lt;/code&gt; and &lt;code&gt;pt_BR&lt;/code&gt; all select Brazilian Portuguese. A bare &lt;code&gt;?lng=pt&lt;/code&gt; resolves to European Portuguese, and a region code for a language shipped without variants still resolves to that language (&lt;code&gt;?lng=de-CH&lt;/code&gt; gives German).&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; In Spanish, French, and Arabic, the sentence on the authorization screen describing what the application would be able to do omitted that the access spans all of the user&amp;rsquo;s calendars, not just one. This is the sentence a user reads before granting access, and it described less access than was actually being requested.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; The button at the bottom of the error screen (&amp;ldquo;Go back&amp;rdquo; / &amp;ldquo;Return to application&amp;rdquo;) rendered in English in every language. The title and message above it were translated correctly, so the English button read as a broken page rather than a missing translation.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; The example Apple ID on the iCloud login screen was translated in Spanish and French (&lt;code&gt;usuario@icloud.com&lt;/code&gt;, &lt;code&gt;utilisateur@icloud.com&lt;/code&gt;) instead of staying &lt;code&gt;user@icloud.com&lt;/code&gt;. A user copying the example rather than reading it as a placeholder would fail to connect with no useful error.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; The Spanish authorization screen addressed the user informally while the iCloud login, CalDAV login, and error screens addressed them formally &amp;mdash; one form on the first screen, another on the next. Every language that distinguishes formal from informal address now uses the formal form on all screens.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; The provider list named Google&amp;rsquo;s product &amp;ldquo;Google Calendar&amp;rdquo; in French and Arabic, where Google ships it as &lt;strong&gt;Google Agenda&lt;/strong&gt; and under its own Arabic name. Provider names now follow each vendor&amp;rsquo;s own naming per market &amp;mdash; the brand stays untouched while the generic word is translated, as in Calendrier iCloud and Calendario de iCloud.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; The Spanish iCloud login screen labelled Apple&amp;rsquo;s two-factor authentication as &lt;code&gt;Autenticaci&amp;oacute;n en dos pasos&lt;/code&gt; &amp;mdash; &amp;ldquo;two-step verification&amp;rdquo;, a different and older Apple mechanism &amp;mdash; while the instructions beneath it describe two-factor. It now reads &lt;code&gt;de dos factores&lt;/code&gt;, matching the English.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.3.2</title><link>https://mobiscroll.com/releases/connect#api-v1.3.2</link><guid isPermaLink="false">1.3.2</guid><description>&lt;h3&gt;Correct event times for Microsoft (Outlook) calendars&lt;/h3&gt;
&lt;p&gt;Fixed an issue where the &lt;code&gt;start&lt;/code&gt; and &lt;code&gt;end&lt;/code&gt; times returned for Microsoft (Outlook) events were off by a fixed number of hours &amp;mdash; 2 hours during European summer time and 1 hour in winter. An event created at 10:00 in a UTC+2 timezone was returned as &lt;code&gt;2026-08-27T06:00:00.000Z&lt;/code&gt; instead of &lt;code&gt;2026-08-27T08:00:00.000Z&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The shift affected every timed Microsoft event in both &lt;code&gt;GET /api/events&lt;/code&gt; and webhook payloads, and all-day Microsoft events could come through on the previous date. It was the same for every account and unrelated to the timezone the event was created in, so calendars rendered from these times were consistently early. Google, iCloud, and CalDAV events were never affected.&lt;/p&gt;
&lt;p&gt;Also fixed a related off-by-one where deleting a recurring Microsoft event with &lt;code&gt;deleteMode: &apos;following&apos;&lt;/code&gt; could end the series one day earlier than intended when the occurrence fell close to midnight.&lt;/p&gt;
&lt;p&gt;No change is required on your side. If you worked around the shift &amp;mdash; adding the missing hours back, or reading the times out of the &lt;code&gt;original&lt;/code&gt; payload instead of the top-level &lt;code&gt;start&lt;/code&gt;/&lt;code&gt;end&lt;/code&gt; &amp;mdash; remove that workaround, as the top-level values are now correct.&lt;/p&gt;
&lt;h3&gt;Events&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; The &lt;code&gt;start&lt;/code&gt; and &lt;code&gt;end&lt;/code&gt; times returned for Microsoft (Outlook) events were off by a fixed number of hours &amp;mdash; 2 hours during European summer time and 1 hour in winter &amp;mdash; in both &lt;code&gt;GET /api/events&lt;/code&gt; and webhook payloads, and all-day events could come through on the previous date. The top-level times are now correct. Google, iCloud, and CalDAV events were never affected.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; Deleting a recurring Microsoft event with &lt;code&gt;deleteMode: &apos;following&apos;&lt;/code&gt; could end the series one day earlier than intended when the occurrence fell close to midnight.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.3.1</title><link>https://mobiscroll.com/releases/connect#api-v1.3.1</link><guid isPermaLink="false">1.3.1</guid><description>&lt;h3&gt;Webhook sync reliability&lt;/h3&gt;
&lt;p&gt;Fixed an issue where webhook notifications could get stuck repeatedly re-sending the same large batch of events &amp;mdash; flagged &lt;code&gt;isInitialSync: true&lt;/code&gt; &amp;mdash; instead of the actual change. This happened when a single change produced more than one page of updates (for Google, over 250 events), such as editing many occurrences of a long recurring series. The incremental sync now pages through every change, so notifications again deliver only the events that actually changed. Affects Google and Outlook calendars.&lt;/p&gt;
&lt;p&gt;The &lt;code&gt;isInitialSync&lt;/code&gt; flag is now set only for an initial-sync delivery, so a large but ordinary change is correctly reported with &lt;code&gt;isInitialSync: false&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;No integration changes are required &amp;mdash; the webhook payload shape is unchanged.&lt;/p&gt;
&lt;h3&gt;Webhooks&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; Webhook notifications for a change that produced many events at once &amp;mdash; for example editing many occurrences of a recurring series &amp;mdash; could get stuck repeatedly re-sending the same large batch instead of the actual change. The incremental sync now pages through every change so notifications deliver the correct events. Affects Google and Outlook.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed:&lt;/strong&gt; The webhook payload&amp;rsquo;s &lt;code&gt;isInitialSync&lt;/code&gt; flag is now set only for an initial-sync delivery. A large but ordinary change (such as editing many occurrences of a recurring series) is reported with &lt;code&gt;isInitialSync: false&lt;/code&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.3.0</title><link>https://mobiscroll.com/releases/connect#api-v1.3.0</link><guid isPermaLink="false">1.3.0</guid><description>&lt;h3&gt;Per-application branding&lt;/h3&gt;
&lt;p&gt;Customize the Connect screens for each of your applications. From the dashboard &lt;strong&gt;Branding&lt;/strong&gt; page you can set a logo (plus an optional dark-mode logo), a primary color, a default theme (auto, light, or dark), and optionally hide the &amp;ldquo;Powered by Mobiscroll Connect&amp;rdquo; footer. The authorization, provider login, and error screens render this branding live, so users get a consistent, on-brand experience throughout the connection flow.&lt;/p&gt;
&lt;p&gt;Branding requires the &lt;strong&gt;Scale&lt;/strong&gt; plan or higher &amp;mdash; on lower plans the Connect screens render the default Mobiscroll branding and the dashboard shows an upgrade notice.&lt;/p&gt;
&lt;p&gt;You can also set an optional &lt;strong&gt;support email&lt;/strong&gt; and &lt;strong&gt;support URL&lt;/strong&gt; from Application Settings; when present they appear as a &amp;ldquo;Need help?&amp;rdquo; contact on the error screen. These are available on every plan.&lt;/p&gt;
&lt;p&gt;No integration changes are required &amp;mdash; branding is optional, and applications without it fall back to the Mobiscroll defaults.&lt;/p&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Customize the Connect screens per application from the dashboard &lt;strong&gt;Branding&lt;/strong&gt; page &amp;mdash; set a logo (plus an optional dark-mode logo), a primary color, a default theme (&lt;code&gt;auto&lt;/code&gt; follows each user&amp;rsquo;s device; the calling app&amp;rsquo;s &lt;code&gt;?theme=&lt;/code&gt; and the user&amp;rsquo;s own choice still take precedence), and optionally hide the &amp;ldquo;Powered by Mobiscroll Connect&amp;rdquo; footer. The authorization, provider login, and error screens render this branding live for an on-brand experience throughout the connection flow.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Per-application branding is available on the &lt;strong&gt;Grow&lt;/strong&gt; and &lt;strong&gt;Scale&lt;/strong&gt; plans. On lower plans the Connect screens use the default Mobiscroll branding and the dashboard Branding page shows an upgrade notice.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Set an optional support email and support URL from &lt;strong&gt;Application Settings&lt;/strong&gt;; when present they appear as a &amp;ldquo;Need help?&amp;rdquo; contact on the Connect error screen. Available on every plan.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Upload a logo and dark-mode logo from the dashboard (PNG, JPG, WebP, or SVG), or paste an image URL. Uploads are optimized and hosted for you.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Turn branding on or off from the Branding page without losing your saved settings or changing your plan.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Brand the Connect screens per application from the dashboard &lt;strong&gt;Branding&lt;/strong&gt; page &amp;mdash; logo, dark-mode logo, primary color, default theme, and an option to hide the footer. The authorization, provider login, and error screens render it live.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Branding is available on the &lt;strong&gt;Scale&lt;/strong&gt; plan or higher; lower plans keep the default Mobiscroll branding.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Add an optional support email or URL in &lt;strong&gt;Application Settings&lt;/strong&gt; to show a &amp;ldquo;Need help?&amp;rdquo; contact on the error screen. Available on every plan.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Redesigned the Connect screens with a cleaner, consistent layout in both light and dark across every screen.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; Error screens now keep the application&amp;rsquo;s branding even when reached after the authorization session has expired or without a client reference, instead of falling back to the default Mobiscroll appearance.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; Error screens keep the application&amp;rsquo;s branding even when the authorization session has expired or no client reference is present.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed:&lt;/strong&gt; Refreshed the Connect screen layout &amp;mdash; uniform provider logos, consistent row alignment and spacing, and action buttons pinned to the bottom of the card across all screens.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.2.0</title><link>https://mobiscroll.com/releases/connect#api-v1.2.0</link><guid isPermaLink="false">1.2.0</guid><description>&lt;h3&gt;A brand-new, personalized Connect experience&lt;/h3&gt;
&lt;p&gt;The Connect pages &amp;mdash; where users link their Google, iCloud, Outlook, and CalDAV calendars &amp;mdash; have been completely redesigned. The connection flow now personalizes itself to the application that initiated it, so users see a familiar, on-brand experience from your app through to their calendar and back.&lt;/p&gt;
&lt;p&gt;You can set a per-application &lt;strong&gt;display name&lt;/strong&gt; from the dashboard; when set, it appears on the authorization and connection-management screens (instead of the generic &amp;ldquo;the application&amp;rdquo;) so users always know which app they are connecting to and where they will return.&lt;/p&gt;
&lt;p&gt;The update also brings refined light and dark themes and a cleaner, fully responsive layout across every screen.&lt;/p&gt;
&lt;p&gt;No integration changes are required &amp;mdash; existing OAuth flows continue to work unchanged.&lt;/p&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; The connection flow now personalizes itself to the application that initiated it. Set a per-application &lt;strong&gt;display name&lt;/strong&gt; from the dashboard and it appears on the authorization and connection-management screens (instead of the generic &amp;ldquo;the application&amp;rdquo;), so users always know which app they are connecting to and where they will return.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed:&lt;/strong&gt; The Connect pages &amp;mdash; where users link their Google, iCloud, Outlook, and CalDAV calendars &amp;mdash; have been completely redesigned, with refined light and dark themes and a cleaner, fully responsive layout across every screen. No integration changes are required; existing OAuth flows continue to work unchanged.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect API 1.1.0</title><link>https://mobiscroll.com/releases/connect#api-v1.1.0</link><guid isPermaLink="false">1.1.0</guid><description>&lt;h3&gt;Connect pages &amp;mdash; Localization&lt;/h3&gt;
&lt;p&gt;The Connect pages (&lt;code&gt;authorize&lt;/code&gt;, &lt;code&gt;consent&lt;/code&gt;, login, and error pages) are now localized in English, Spanish, French, and Arabic. Pass &lt;code&gt;?lng=&amp;lt;code&amp;gt;&lt;/code&gt; on the authorize URL to choose the language; without it the UI falls back to the browser &lt;code&gt;Accept-Language&lt;/code&gt; header, then English.&lt;/p&gt;
&lt;p&gt;Arabic is the first RTL locale &amp;mdash; the Connect UI switches to right-to-left automatically.&lt;/p&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;p&gt;The OAuth callback redirect URL no longer includes encoded token data; it now passes &lt;code&gt;connected=true&lt;/code&gt;, preventing URL-length errors for Microsoft OAuth flows and avoiding token exposure in browser history and logs.&lt;/p&gt;
&lt;h3&gt;OAuth&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Connect pages (&lt;code&gt;authorize&lt;/code&gt;, &lt;code&gt;apple-login&lt;/code&gt;, &lt;code&gt;caldav-login&lt;/code&gt;, &lt;code&gt;consent&lt;/code&gt;, &lt;code&gt;error-page&lt;/code&gt;, &lt;code&gt;session-lost&lt;/code&gt;) are now localized. Supported languages: English (&lt;code&gt;en&lt;/code&gt;), Spanish (&lt;code&gt;es&lt;/code&gt;), French (&lt;code&gt;fr&lt;/code&gt;), and Arabic (&lt;code&gt;ar&lt;/code&gt;).&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Connect page language is selected via the &lt;code&gt;?lng=&amp;lt;code&amp;gt;&lt;/code&gt; query parameter on the authorize URL, the recommended way for calling applications to pass a locale (e.g. &lt;code&gt;?lng=es&lt;/code&gt;).&lt;/li&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Arabic (&lt;code&gt;ar&lt;/code&gt;) is the first RTL locale; the Connect UI direction switches to right-to-left automatically when it is active.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed:&lt;/strong&gt; The OAuth callback redirect URL no longer includes encoded token data in the query string. The callback now passes &lt;code&gt;connected=true&lt;/code&gt; instead, preventing URL length errors for Microsoft OAuth flows and avoiding token exposure in browser history and server logs.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed:&lt;/strong&gt; When &lt;code&gt;?lng=&lt;/code&gt; is not provided, the Connect UI now falls back to the user&amp;rsquo;s browser &lt;code&gt;Accept-Language&lt;/code&gt; header, then defaults to English. To explicitly force English, pass &lt;code&gt;?lng=en&lt;/code&gt;.&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Mobiscroll Connect Node.js SDK 1.1.0</title><link>https://mobiscroll.com/releases/connect#nodejs-sdk-v1.1.0</link><guid isPermaLink="false">nodejs-sdk-1.1.0</guid><description>&lt;h3&gt;Localization support&lt;/h3&gt;
&lt;p&gt;Added an optional &lt;code&gt;lng&lt;/code&gt; parameter to &lt;code&gt;generateAuthUrl&lt;/code&gt; so the Connect authorization pages render in the chosen language (&lt;code&gt;en&lt;/code&gt;, &lt;code&gt;es&lt;/code&gt;, &lt;code&gt;fr&lt;/code&gt;, &lt;code&gt;ar&lt;/code&gt;).&lt;/p&gt;
&lt;h3&gt;SDK&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;New:&lt;/strong&gt; Added an optional &lt;code&gt;lng&lt;/code&gt; parameter to &lt;code&gt;generateAuthUrl&lt;/code&gt; for localizing the Connect authorization pages (supported: &lt;code&gt;en&lt;/code&gt;, &lt;code&gt;es&lt;/code&gt;, &lt;code&gt;fr&lt;/code&gt;, &lt;code&gt;ar&lt;/code&gt;).&lt;/li&gt;&lt;/ul&gt;</description><pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate></item></channel></rss>