API

What's New

Webhooks

Subscriptions, deliveries and their payloads are corrected.

Events

Event responses, free-busy results and request validation are corrected.

iCloud and CalDAV

Conference URLs, event IDs and updates are corrected for both providers.

Disconnect and revoke

Both endpoints handle more cases correctly.

Events

Fixed
  • We added the missing url, the join URL, to conferenceData in GET /api/events, in the POST and PUT /api/event responses and in webhook deliveries.
  • We added the missing original to conferenceData in the same responses and deliveries: the conference data exactly as the calendar provider returns it, Google’s conferenceData or Microsoft’s onlineMeeting.
  • We fixed GET /api/events with the free-busy scope returning the description of Outlook, iCloud and CalDAV events and the conference of CalDAV events. Both are now left out, as description already was for Google.
  • We fixed iCloud and CalDAV URLs set in Apple Calendar missing from conference. They are now returned in conference and conferenceData, as URLs set through Connect already were.
  • The conference of an iCloud or CalDAV event is the URL set on the event. It can be any URL, not only a meeting link.
  • We fixed PUT /api/event changing the iCal UID of an iCloud or CalDAV event. An iCloud event got its id followed by @mobiscroll.com as the UID, and a CalDAV event got the eventId of the request. The event now keeps the UID it already has.
  • We fixed GET /api/events answering 500 when calendarIds or nextPageToken is not valid JSON. It now returns 400 with an error naming the parameter.

Webhooks

Fixed
  • We fixed POST /api/subscribe-webhook replacing another user’s subscription when called with that subscription’s channelId, so its owner stopped receiving webhooks. It now returns 409 with { "error": "channelId is already in use" } and leaves the other subscription untouched.
  • We fixed POST /api/oauth/disconnect with account 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 Disconnect Account.
  • 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.
  • We fixed deleted Outlook, iCloud and CalDAV events arriving in webhook deliveries without calendarId. Every delivered event now has it.
  • We added the missing conferenceData to webhook deliveries. Every event that has a conference now carries it, in the shape GET /api/events returns. See Client webhook payload.
  • We fixed iCloud and CalDAV event ids in webhook deliveries differing from GET /api/events, so a deleted event or series could not be matched to its earlier deliveries. Created and updated iCloud events, and the PUT /api/event response for an iCloud event, used the iCal UID as id; deleted CalDAV events used the file name of the calendar object. They now use the id of GET /api/events: 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.

OAuth

Fixed
  • We fixed POST /api/oauth/revoke with an expired access token returning 200 without revoking anything, so the refresh token kept working. It now revokes the user’s access and refresh tokens. See Revoke Token.
  • We fixed POST /api/oauth/disconnect accepting any provider value. A missing or unknown provider now returns 400 with { "error": "Missing or invalid provider" }.

What's New

This release changes how Connect delivers webhooks and how it handles token refreshes that come from more than one process.

Webhooks

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.

Concurrent token refreshes

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’s connection.

Webhooks

New
  • 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.
  • 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 5xx, 408 or 429. Any other 4xx, and any 3xx, is not retried. Every attempt at one delivery carries the same webhook-id.
  • Connect no longer follows redirects from your webhook URL. A 3xx response counts as a failed delivery, so a URL that redirects, for example from http:// to https://, needs to be set to its final address.

OAuth

New
  • 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.
  • 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.
  • Every account in GET /api/oauth/connection-status also carries syncState and syncStateUpdatedAt. syncState reads reauth_required once Google or Outlook has rejected the stored credentials, and the user has to reconnect before their calendars sync again. See Connection health.

What's New

This release contains fixes, with a focus on users who connect several accounts, calendar details, and webhook reliability.

Multi-Account Fixes

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.

Calendar Ownership

GET /calendars now tells you which account owns each calendar and whether it can be written to.

Webhook Reliability

Google and Outlook channels keep running without intervention, and CalDAV delivery needs no separate setup.

Events

New
  • We added the account and readOnly fields to every calendar returned by GET /calendars, on all four providers.
Fixed
  • We fixed an issue where POST, PUT and DELETE /event returned 400 for a calendar belonging to any Google account other than the first one the user connected.
  • 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’s calendar app.
  • We fixed the calendarIds filter of GET /events 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.
  • We fixed an issue where all-day events on iCloud and CalDAV calendars could come back from GET /events dated one day earlier than the calendar shows.
  • We fixed an issue on iCloud and CalDAV calendars where GET /events could return link as { params, val } instead of a URL string.

Webhooks

Fixed
  • We fixed an issue where a webhook subscription could not be created for those same Google calendars, so their changes never reached your webhook.
  • 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 subscribe-webhook. Delivery now starts automatically, matching Google, Outlook and iCloud.
  • 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.

OAuth

Fixed
  • 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 “Session Expired” message.

General

New
  • 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.

What's New

Event identifiers on iCloud calendars

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.

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.

Events

Fixed
  • 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.
  • Update and delete now accept both identifiers, so anything you stored before this release keeps working. If you worked around this by trimming “@mobiscroll.com” off the identifier, that is no longer necessary — but never do it on CalDAV calendars, where the full value is the identifier.
  • On iCloud and CalDAV calendars, update and delete could act on the wrong event, or fail to find one that was listed.

What's New

37 languages on the Connect pages

Connect’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.

Two details are worth checking if you pass ?lng= explicitly. Chinese is now selected by script — zh-Hans or zh-Hant — with the familiar region codes mapped onto them. Ukrainian is uk, the language code, rather than the country code. Everything else continues to work as before: ?lng= wins, Accept-Language decides otherwise, and API responses stay English.

OAuth

New
  • The Connect pages are now localized in 37 languages, 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.
  • Hebrew (he) and Persian (fa) join Arabic as right-to-left languages; the Connect pages switch direction automatically when one of them is active.
  • Chinese is selected by script rather than region: ?lng=zh-Hans for Simplified and ?lng=zh-Hant for Traditional. zh-CN, zh-SG and zh-MY resolve to Simplified; zh-TW, zh-HK and zh-MO to Traditional; a bare zh to Simplified.
  • Ukrainian uses the ISO 639-1 language code ?lng=uk. The country code ua is accepted as an alias, so either value works.
  • Languages are also matched under the codes browsers commonly send: nb and nb-NO for Norwegian, iw for Hebrew, ru-UA and ru-BY for Russian, and en-AU, en-NZ, en-IE and en-ZA for British English. No change is needed for Accept-Language to pick them up.

What's New

Calendar access that was never granted

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.

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 — two new fields tell you which of them to send back through the flow.

Events

Fixed
  • Where no connected account has calendar access, GET /calendars, GET /events and the /event write endpoints now return 403 with code: "calendar_permission_required" and an accounts array naming who must reconnect, instead of an empty list. A request that used to return an empty array can now be a 403 — 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 X-Connect-Calendar-Permission-Missing header.

OAuth

New
  • Every account in GET /api/oauth/connection-status now carries grantedScopes and calendarPermissionGranted. The flag is evaluated against the calling request’s scope, so a grant sufficient for free-busy can still be false for read-write; it is null for Apple and CalDAV, which have no permissions to withhold. Check it before showing a calendar picker — see the Scopes & Permissions docs page.
Fixed
  • Google shows the calendar permission as a separate checkbox. Leaving it unticked still produced a valid sign-in, so the account looked connected while GET /calendars returned [] 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 — providers only issue permissions at consent time, so those users must reconnect.

What's New

Microsoft webhook payloads and echo filtering

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.

Read the second fix before touching your handler — 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 custom as a second line of defence; on Microsoft it finally survives the round trip.

Webhooks

Fixed
  • Webhook deliveries for Microsoft (Outlook) events now include custom, matching what GET /events returns for the same event. Microsoft rows previously arrived without it, and without original.extensions, so an origin marker such as custom.source = "my-system" never reached your endpoint. Google was unaffected.
  • Webhook echoes of your own POST /event, PUT /event and DELETE /event 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.

What's New

Application verification

Mobiscroll can now review your application and mark it verified. This is our review, not the calendar providers’ — Mobiscroll owns the upstream Google and Microsoft OAuth applications, so you never run Google brand verification or a Microsoft publisher review yourself.

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.

OAuth

New
  • 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 Verification page of your application in the dashboard. Verification is optional and gates nothing — it does not unlock features, change any plan limit, or affect the Connect API. See App Verification docs page for what a reviewer checks, the details you need to supply, and which changes send an application back for review.

What's New

Correct Google attendee lists, and four new languages

A correctness fix for anyone reading Google events: attendees 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 — one case still needs it.

The Connect screens gain four languages for a total of eight, and lng now takes region-qualified codes, which is what makes European and Brazilian Portuguese separately selectable. The languages that shipped earlier also received copy corrections.

Events

Fixed
  • For a Google event whose organizer is a group calendar, that calendar’s address (ending in @group.calendar.google.com) was added to attendees with "status": "accepted" even when Google did not list it as a guest — a participant that was not on the event, marked as having accepted an invitation it never received. The attendees 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 "organizer": true, including a group calendar’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.
  • A Google event with no guests returned a one-entry attendees list holding the organizer, instead of an empty list. Microsoft, iCloud, and CalDAV events are unaffected — those protocols keep the organizer outside the guest list, so the organizer is still added there as an "organizer": true entry.

OAuth

New
  • The Connect screens are now available in German (de), Italian (it), European Portuguese (pt-PT), and Brazilian Portuguese (pt-BR), bringing the total to eight languages alongside English, Spanish, French, and Arabic. Select one with ?lng=<code> on the authorize URL, or let the browser Accept-Language header pick it automatically.
  • lng now accepts region-qualified codes, so European and Brazilian Portuguese are separate languages. Codes are written with a hyphen, as in pt-BR; matching is case-insensitive, and an underscore is accepted in place of the hyphen, so pt-br, PT-BR and pt_BR all select Brazilian Portuguese. A bare ?lng=pt resolves to European Portuguese, and a region code for a language shipped without variants still resolves to that language (?lng=de-CH gives German).
Fixed
  • 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’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.
  • The button at the bottom of the error screen (“Go back” / “Return to application”) 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.
  • The example Apple ID on the iCloud login screen was translated in Spanish and French (usuario@icloud.com, utilisateur@icloud.com) instead of staying user@icloud.com. A user copying the example rather than reading it as a placeholder would fail to connect with no useful error.
  • The Spanish authorization screen addressed the user informally while the iCloud login, CalDAV login, and error screens addressed them formally — 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.
  • The provider list named Google’s product “Google Calendar” in French and Arabic, where Google ships it as Google Agenda and under its own Arabic name. Provider names now follow each vendor’s own naming per market — the brand stays untouched while the generic word is translated, as in Calendrier iCloud and Calendario de iCloud.
  • The Spanish iCloud login screen labelled Apple’s two-factor authentication as Autenticación en dos pasos — “two-step verification”, a different and older Apple mechanism — while the instructions beneath it describe two-factor. It now reads de dos factores, matching the English.

What's New

Correct event times for Microsoft (Outlook) calendars

Fixed an issue where the start and end times returned for Microsoft (Outlook) events were off by a fixed number of hours — 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 2026-08-27T06:00:00.000Z instead of 2026-08-27T08:00:00.000Z.

The shift affected every timed Microsoft event in both GET /api/events 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.

Also fixed a related off-by-one where deleting a recurring Microsoft event with deleteMode: 'following' could end the series one day earlier than intended when the occurrence fell close to midnight.

No change is required on your side. If you worked around the shift — adding the missing hours back, or reading the times out of the original payload instead of the top-level start/end — remove that workaround, as the top-level values are now correct.

Events

Fixed
  • The start and end times returned for Microsoft (Outlook) events were off by a fixed number of hours — 2 hours during European summer time and 1 hour in winter — in both GET /api/events 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.
  • Deleting a recurring Microsoft event with deleteMode: 'following' could end the series one day earlier than intended when the occurrence fell close to midnight.

What's New

Webhook sync reliability

Fixed an issue where webhook notifications could get stuck repeatedly re-sending the same large batch of events — flagged isInitialSync: true — 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.

The isInitialSync flag is now set only for an initial-sync delivery, so a large but ordinary change is correctly reported with isInitialSync: false.

No integration changes are required — the webhook payload shape is unchanged.

Webhooks

Fixed
  • Webhook notifications for a change that produced many events at once — for example editing many occurrences of a recurring series — 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.
Changed
  • The webhook payload’s isInitialSync 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 isInitialSync: false.

What's New

Per-application branding

Customize the Connect screens for each of your applications. From the dashboard Branding 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 “Powered by Mobiscroll Connect” footer. The authorization, provider login, and error screens render this branding live, so users get a consistent, on-brand experience throughout the connection flow.

Branding requires the Scale plan or higher — on lower plans the Connect screens render the default Mobiscroll branding and the dashboard shows an upgrade notice.

You can also set an optional support email and support URL from Application Settings; when present they appear as a “Need help?” contact on the error screen. These are available on every plan.

No integration changes are required — branding is optional, and applications without it fall back to the Mobiscroll defaults.

OAuth

New
  • Customize the Connect screens per application from the dashboard Branding page — set a logo (plus an optional dark-mode logo), a primary color, a default theme (auto follows each user’s device; the calling app’s ?theme= and the user’s own choice still take precedence), and optionally hide the “Powered by Mobiscroll Connect” footer. The authorization, provider login, and error screens render this branding live for an on-brand experience throughout the connection flow.
  • Per-application branding is available on the Grow and Scale plans. On lower plans the Connect screens use the default Mobiscroll branding and the dashboard Branding page shows an upgrade notice.
  • Set an optional support email and support URL from Application Settings; when present they appear as a “Need help?” contact on the Connect error screen. Available on every plan.
  • 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.
  • Turn branding on or off from the Branding page without losing your saved settings or changing your plan.
  • Brand the Connect screens per application from the dashboard Branding page — 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.
  • Branding is available on the Scale plan or higher; lower plans keep the default Mobiscroll branding.
  • Add an optional support email or URL in Application Settings to show a “Need help?” contact on the error screen. Available on every plan.
  • Redesigned the Connect screens with a cleaner, consistent layout in both light and dark across every screen.
Fixed
  • Error screens now keep the application’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.
  • Error screens keep the application’s branding even when the authorization session has expired or no client reference is present.
Changed
  • Refreshed the Connect screen layout — uniform provider logos, consistent row alignment and spacing, and action buttons pinned to the bottom of the card across all screens.

What's New

A brand-new, personalized Connect experience

The Connect pages — where users link their Google, iCloud, Outlook, and CalDAV calendars — 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.

You can set a per-application display name from the dashboard; when set, it appears on the authorization and connection-management screens (instead of the generic “the application”) so users always know which app they are connecting to and where they will return.

The update also brings 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.

OAuth

New
  • The connection flow now personalizes itself to the application that initiated it. Set a per-application display name from the dashboard and it appears on the authorization and connection-management screens (instead of the generic “the application”), so users always know which app they are connecting to and where they will return.
Changed
  • The Connect pages — where users link their Google, iCloud, Outlook, and CalDAV calendars — 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.

What's New

Connect pages — Localization

The Connect pages (authorize, consent, login, and error pages) are now localized in English, Spanish, French, and Arabic. Pass ?lng=<code> on the authorize URL to choose the language; without it the UI falls back to the browser Accept-Language header, then English.

Arabic is the first RTL locale — the Connect UI switches to right-to-left automatically.

OAuth

The OAuth callback redirect URL no longer includes encoded token data; it now passes connected=true, preventing URL-length errors for Microsoft OAuth flows and avoiding token exposure in browser history and logs.

OAuth

New
  • Connect pages (authorize, apple-login, caldav-login, consent, error-page, session-lost) are now localized. Supported languages: English (en), Spanish (es), French (fr), and Arabic (ar).
  • Connect page language is selected via the ?lng=<code> query parameter on the authorize URL, the recommended way for calling applications to pass a locale (e.g. ?lng=es).
  • Arabic (ar) is the first RTL locale; the Connect UI direction switches to right-to-left automatically when it is active.
Fixed
  • The OAuth callback redirect URL no longer includes encoded token data in the query string. The callback now passes connected=true instead, preventing URL length errors for Microsoft OAuth flows and avoiding token exposure in browser history and server logs.
Changed
  • When ?lng= is not provided, the Connect UI now falls back to the user’s browser Accept-Language header, then defaults to English. To explicitly force English, pass ?lng=en.

What's New

OAuth

Extended session, oauth_req cookie, and client-side transaction TTL from 30 minutes to 2 hours to prevent premature session expiry during authorization.

On session expiry or transaction loss, the error page now shows a “Return to application” button that navigates to the client app’s redirect_uri.

Improved error messages on the authorization page and server-rendered error pages to clearly indicate session expiry rather than showing a generic “invalid client” message.

OAuth

Changed
  • Extended session, oauth_req cookie, and client-side transaction TTL from 30 minutes to 2 hours to prevent premature session expiry during authorization.
  • On session expiry or transaction loss during the authorization decision, the error page now shows a “Return to application” button that navigates to the client app’s redirect_uri instead of returning to the previous page.
  • Improved error messages on the authorization page and server-rendered error pages to clearly indicate session expiry rather than showing a generic “invalid client” message.

What's New

OAuth

Bearer-token authentication is now supported alongside OAuth session cookies for disconnect and connection-status endpoints. Improved auth-context handling for OAuth request cookies.

Webhooks & CalDAV

Added CalDAV provider support in webhook receiver processing with polling-based change detection for created, updated, and deleted events.

Events & Conference Links

Added conferenceData field to event responses, exposing provider-specific metadata alongside the existing conference URL string.

Create and update event endpoints now accept a conferenceData object for provider-specific conference configuration (e.g. auto-generating a Google Meet or Teams link).

Events

New
  • Added conferenceData field to event responses, exposing provider-specific metadata (provider, autoGenerate, raw provider data) alongside the existing conference URL string.
  • Create and update event endpoints now accept a conferenceData object for passing provider-specific conference configuration (e.g. auto-generating a Google Meet or Teams link).

Webhooks

New
  • Added CalDAV provider support in webhook receiver processing, including polling-based change payload handling.
  • Added polling-based CalDAV change detection for created/updated/deleted events, aligned with Apple polling sync behavior.

OAuth

Fixed
  • Improved auth-context handling for OAuth request cookies to avoid invalid-cookie parsing issues.
Changed
  • Changed POST /api/oauth/disconnect and GET /api/oauth/connection-status to support Bearer-token authentication in addition to OAuth session cookies.

What's New

OAuth

Added refresh token support for public OAuth clients in the token exchange flow, together with a new endpoint for refreshing access tokens and revoke functionality.

OAuth

New
  • Added refresh token support for public OAuth clients in the token exchange flow together with a new endpoint for refreshing access tokens using refresh tokens and revoke functionality.

What's New

Database

Fixed a type mismatch for projectId in database queries.

Events

Added lastModified as a top-level field in the Event object.

Webhooks

Added userId as a top-level field in the webhook notification.

Added dedup handler functionality for echo webhook notifications to avoid notification loops (preventing notifications for events you just updated).

Database

Fixed
  • Resolved a type mismatch for projectId in database queries.

Events

New
  • Added lastModified as a top-level field in the Event object.

Webhooks

New
  • Added userId as a top-level field in the webhook notification.
  • Added dedup handler functionality for echo webhook notifications to avoid notification loops (preventing notifications for events you just updated).

SDKs

Node.js SDK

What's New

Event types

Event dates are typed as the ISO strings the SDK returns.

Missing API features

Revoke, calendar account and readOnly, meeting fields on event writes and the theme option are now covered.

Webhook types

Webhook event types now match what a delivery carries.

Events
Fixed
  • We fixed the EventCreateData and EventUpdateData types missing conference and conferenceData, so TypeScript rejected { autoGenerate: true } in an object literal. The SDK already sent both fields at runtime.
  • We added the missing url and original to the ConferenceData type. The API returns both from 1.6.1.
  • We fixed the declared type of start and end on events from events.list(), events.create() and events.update(). It is now string, the ISO 8601 strings the SDK returns; it was Date, so calling Date methods on them threw.
  • We fixed the Calendar type missing account and readOnly. Both were already present at runtime.
Webhooks
Fixed
  • We fixed the return type of verifyWebhook() declaring start and end as Date. They are typed string, the ISO 8601 strings the SDK returns.
  • WebhookEvent.original is now typed optional: deleted Outlook, iCloud and CalDAV events in a verifyWebhook() delivery arrive without it.
  • We fixed the type of WebhookEvent.conference, which was declared string. It is now WebhookConference, the object a verifyWebhook() delivery carries, with url, provider, meetingProvider and data.
  • WebhookEvent.lastModified is now typed as always present: every event in a verifyWebhook() delivery has it.
OAuth
Fixed
  • We added the missing auth.revoke(), which revokes every access and refresh token of the user through POST /api/oauth/revoke. See Revoke Token.
  • We fixed generateAuthUrl() not accepting theme. It now accepts light, dark or auto, which sets the color scheme of the Connect pages.

What's New

Webhook verification

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.

SDK
New
  • The SDK now exposes verifyWebhook on webhooks. It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or throws WebhookVerificationError with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. See verifyWebhook.

What's New

Package metadata

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.

SDK
New
  • Package metadata only — 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.

What's New

Webhook subscription management

The SDK now wraps the API’s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.

SDK
New
  • The SDK now exposes subscribeWebhook and unsubscribeWebhook on webhooks, wrapping the API’s POST /subscribe-webhook and POST /unsubscribe-webhook endpoints — previously only reachable with a raw HTTP call.

What's New

Calendar access that was never granted

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.

Unrelated: the event model catches up with three fields it never mapped.

SDK
New
  • The event model now exposes description, conferenceData and lastModified. 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.
  • A calendar or event call where no connected account has calendar access now raises CalendarPermissionError, with an accounts property. It subclasses AuthenticationError, so existing handlers keep working while new code can read which accounts must reconnect.
  • ConnectedAccount gained grantedScopes and calendarPermissionGranted, so getConnectionStatus reports which connected accounts withheld calendar access and cannot list calendars.

What's New

Localization support

Added an optional lng parameter to generateAuthUrl so the Connect authorization pages render in the chosen language (en, es, fr, ar).

SDK
New
  • Added an optional lng parameter to generateAuthUrl for localizing the Connect authorization pages (supported: en, es, fr, ar).

What's New

Initial release

Released the initial version of the Node.js SDK for Mobiscroll Connect.

SDK
New
  • Released the initial version of the Node.js SDK for Mobiscroll Connect.

PHP SDK

What's New

Event writes

Creating and updating an event returns the event instead of raising an error.

Webhook verification

Deliveries with a meeting on an event now verify.

Missing API features

Revoke, calendar account and readOnly and the theme option are now covered.

Events
Fixed
  • We added the missing account and readOnly to Calendar objects. The API returns both for every calendar.
  • We fixed events()->create() and events()->update() throwing ServerError on every successful write. They now return the written event.
Webhooks
Fixed
  • We fixed verifyWebhook() rejecting every delivery whose events include a conference, with reason invalid_payload, because a delivery carries conference as an object. Those deliveries now verify: $conference is the join URL of that object, and $conferenceData is the delivery’s conferenceData, or one built from the object when the delivery has none.
OAuth
Fixed
  • We added the missing auth()->revoke(), which revokes every access and refresh token of the user through POST /api/oauth/revoke. See Revoke Token.
  • We fixed generateAuthUrl() not accepting theme. It now accepts light, dark or auto, which sets the color scheme of the Connect pages.
  • We fixed the default scope of generateAuthUrl(). It is now read-write; it was calendar, which is not a Connect scope. Connect treated it as read-write, so the authorization behaves the same.

What's New

Webhook verification

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.

SDK
New
  • The SDK now exposes verifyWebhook on webhooks(). It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or throws WebhookVerificationError with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. Requires the sodium PHP extension and adds psr/simple-cache. Under PHP-FPM, pass a PSR-16 cache in webhookKeyCache so the keys are not fetched on every request. See verifyWebhook.

What's New

Package metadata

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.

SDK
New
  • Package metadata only — 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.

What's New

Webhook subscription management

The SDK now wraps the API’s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.

SDK
New
  • The SDK now exposes subscribeWebhook and unsubscribeWebhook on webhooks, wrapping the API’s POST /subscribe-webhook and POST /unsubscribe-webhook endpoints — previously only reachable with a raw HTTP call.

What's New

Calendar access that was never granted

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.

Unrelated: the event model catches up with three fields it never mapped.

SDK
New
  • The event model now exposes description, conferenceData and lastModified. 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.
  • A calendar or event call where no connected account has calendar access now raises CalendarPermissionError, with getAccounts(). It extends AuthenticationError, so existing handlers keep working while new code can read which accounts must reconnect.
  • Each account returned by getConnectionStatus now carries grantedScopes and calendarPermissionGranted, reporting which connected accounts withheld calendar access and cannot list calendars.

What's New

Localization support

Added an optional lng parameter to generateAuthUrl so the Connect authorization pages render in the chosen language (en, es, fr, ar).

SDK
New
  • Added an optional lng parameter to generateAuthUrl for localizing the Connect authorization pages (supported: en, es, fr, ar).

What's New

Breaking changes — Node SDK parity

Removed ConnectionStatusResponse::$limit. The response only exposes $connections and $limitReached.

Migration: reading $response->limit now raises an undefined property error.

SDK
Changed
  • Removed ConnectionStatusResponse::$limit for Node SDK parity. The response exposes only $connections and $limitReached.

What's New

Initial release

Released the initial version of the PHP SDK for Mobiscroll Connect.

SDK
New
  • Released the initial version of the PHP SDK for Mobiscroll Connect.

.NET SDK

What's New

Webhook verification

Deliveries with a meeting on an event now verify.

Missing API features

Revoke, calendar Account and ReadOnly, meeting fields on event writes and the Theme option are now covered.

Unknown providers

Responses from a newer Connect with a new calendar provider are read instead of rejected.

Events
Fixed
  • We added the missing Account and ReadOnly to Calendar objects. The API returns both for every calendar.
  • We added the missing Conference and ConferenceData to EventCreateData and EventUpdateData. AutoGenerate = true creates a meeting link.
  • We fixed a provider value this SDK version does not know, sent by a newer Connect, failing the whole Events.ListAsync() response or VerifyWebhookAsync() delivery. It is now read as the new Provider.Unknown.
Webhooks
Fixed
  • We fixed VerifyWebhookAsync() rejecting every delivery whose events include a conference, with reason InvalidPayload, because a delivery carries conference as an object. Those deliveries now verify: Conference is the join URL of that object, and ConferenceData is the delivery’s conferenceData, or one built from the object when the delivery has none.
OAuth
Fixed
  • We added the missing Auth.RevokeAsync(), which revokes every access and refresh token of the user through POST /api/oauth/revoke. See Revoke Token.
  • We fixed AuthorizeParams not accepting a theme. AuthorizeParams.Theme now accepts light, dark or auto, which sets the color scheme of the Connect pages.

What's New

Webhook verification

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.

SDK
New
  • The SDK now exposes VerifyWebhookAsync on Webhooks. It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or throws WebhookVerificationException 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 NSec.Cryptography package. See VerifyWebhookAsync.

What's New

Package metadata

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.

SDK
New
  • Package metadata only — 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.

What's New

Webhook subscription management

The SDK now wraps the API’s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.

SDK
New
  • The SDK now exposes SubscribeWebhookAsync and UnsubscribeWebhookAsync on Webhooks, wrapping the API’s POST /subscribe-webhook and POST /unsubscribe-webhook endpoints — previously only reachable with a raw HTTP call.

What's New

Calendar access that was never granted

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.

Unrelated: the event model catches up with three fields it never mapped.

SDK
New
  • The event model now exposes Description, ConferenceData and LastModified. 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.
  • A calendar or event call where no connected account has calendar access now raises CalendarPermissionException, with an Accounts property. It derives from AuthenticationException, so existing handlers keep working while new code can read which accounts must reconnect.
  • ConnectedAccount gained GrantedScopes and CalendarPermissionGranted, so GetConnectionStatusAsync reports which connected accounts withheld calendar access and cannot list calendars.

What's New

Localization support

Added an optional Lng property to AuthorizeParams so the Connect authorization pages render in the chosen language (en, es, fr, ar) via GenerateAuthUrl.

SDK
New
  • Added an optional Lng property to AuthorizeParams for localizing the Connect authorization pages via GenerateAuthUrl (supported: en, es, fr, ar).

What's New

Breaking changes — Node SDK parity

Changed ConnectionStatusResponse.Connections from a strongly-typed ProviderConnections class to Dictionary<string, List<ConnectedAccount>> keyed by the lowercase provider name (google, microsoft, apple, caldav). The ProviderConnections class has been removed.

Removed ConnectionStatusResponse.Limit.

Bug fix

Fixed a wire-format bug where CalDAV accounts silently failed to deserialize. The previous CalDav property serialized as calDav under JsonNamingPolicy.CamelCase, while the API returns caldav. CalDAV accounts now appear correctly under Connections["caldav"].

Migration: replace status.Connections.Google with status.Connections["google"] (or use TryGetValue to avoid KeyNotFoundException); status.Limit is removed.

SDK
Fixed
  • Fixed a wire-format bug where CalDAV accounts silently failed to deserialize because the old CalDav property serialized as calDav under JsonNamingPolicy.CamelCase, while the API returns caldav.
Changed
  • Changed ConnectionStatusResponse.Connections to Dictionary<string, List<ConnectedAccount>> keyed by the lowercase provider name; the strongly-typed ProviderConnections class has been removed.
  • Removed ConnectionStatusResponse.Limit for Node SDK parity.

What's New

Initial release

Released the initial version of the .NET SDK for Mobiscroll Connect.

SDK
New
  • Released the initial version of the .NET SDK for Mobiscroll Connect.

Python SDK

What's New

Event writes

Creating and updating an event returns the event instead of raising an error.

Missing API features

Revoke, calendar account and read_only, meeting fields on event writes and the theme option are now covered.

Webhook types

The webhook conference is annotated as the object a delivery carries.

Events
Fixed
  • We added the missing account and read_only to Calendar objects. The API returns both for every calendar.
  • We added the missing conference_data key to events.create() and events.update(), which send it as conferenceData, so {"autoGenerate": True} creates a meeting link. conference takes a meeting URL.
  • We fixed events.create() and events.update() raising ServerError on every successful write, on the sync and async clients. They now return the written event.
Webhooks
Fixed
  • We fixed the annotation of WebhookEvent.conference, which was str | None. It is now Mapping[str, Any] | None, the dict a verify_webhook() delivery carries, with url, provider, meetingProvider and data.
OAuth
Fixed
  • We added the missing auth.revoke(), on the sync and async clients, which revokes every access and refresh token of the user through POST /api/oauth/revoke. See Revoke Token.
  • We fixed generate_auth_url() not accepting theme, on the sync and async clients. It now accepts light, dark or auto, which sets the color scheme of the Connect pages.
  • We fixed the default scope of generate_auth_url(), on the sync and async clients. It is now read-write; it was calendar, which is not a Connect scope. Connect treated it as read-write, so the authorization behaves the same.

What's New

Webhook verification

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.

SDK
New
  • The SDK now exposes verify_webhook on webhooks (sync and async clients). It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or raises WebhookVerificationError 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 cryptography package. See verify_webhook.

What's New

Package metadata

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.

SDK
New
  • Package metadata only — 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.

What's New

Webhook subscription management

The SDK now wraps the API’s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.

SDK
New
  • The SDK now exposes subscribe_webhook and unsubscribe_webhook on webhooks (sync and async clients), wrapping the API’s POST /subscribe-webhook and POST /unsubscribe-webhook endpoints — previously only reachable with a raw HTTP call.

What's New

Calendar access that was never granted

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.

Unrelated: the event model catches up with three fields it never mapped.

SDK
New
  • The event model now exposes description, conference_data and last_modified. 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.
  • A calendar or event call where no connected account has calendar access now raises CalendarPermissionError, with an accounts attribute. It subclasses AuthenticationError, so existing handlers keep working while new code can read which accounts must reconnect.
  • ConnectedAccount gained granted_scopes and calendar_permission_granted, so get_connection_status reports which connected accounts withheld calendar access and cannot list calendars.

What's New

Localization support

Added an optional lng keyword argument to generate_auth_url so the Connect authorization pages render in the chosen language (en, es, fr, ar).

SDK
New
  • Added an optional lng keyword argument to generate_auth_url for localizing the Connect authorization pages (supported: en, es, fr, ar).

What's New

Breaking changes — Node SDK parity

Removed CalendarEvent.description. Node’s CalendarEvent response never carried description (only Calendar does). The description field on event create/update input is still accepted.

Removed ConnectionStatusResponse.limit. The response only exposes connections and limit_reached.

Migration: reading event.description or connection_status.limit will now raise AttributeError.

SDK
Changed
  • Removed CalendarEvent.description from the response model for Node SDK parity (only Calendar carries description). The description field on event create/update input is still accepted.
  • Removed ConnectionStatusResponse.limit for Node SDK parity. The response exposes only connections and limit_reached.

What's New

Initial release

Released the initial version of the Python SDK for Mobiscroll Connect.

SDK
New
  • Released the initial version of the Python SDK for Mobiscroll Connect.

Java SDK

What's New

Webhook verification

Deliveries with a meeting on an event now verify.

Missing API features

Revoke, calendar getAccount() and getReadOnly(), meeting fields on event writes and the theme option are now covered.

Unknown providers

Responses from a newer Connect with a new calendar provider are read instead of rejected.

Events
Fixed
  • We added the missing getAccount() and getReadOnly() to Calendar objects. The API returns both for every calendar.
  • We added the missing conference() and conferenceData() to the EventCreateData and EventUpdateData builders. autoGenerate(true) creates a meeting link.
  • We fixed a provider value this SDK version does not know, sent by a newer Connect, failing the whole events().list() response or verifyWebhook() delivery. getProvider() now returns null for it; Provider.fromWire() throws for it.
Webhooks
Fixed
  • We fixed verifyWebhook() rejecting every delivery whose events include a conference, with reason INVALID_PAYLOAD, because a delivery carries conference as an object. Those deliveries now verify: getConference() is the join URL of that object, and getConferenceData() is the delivery’s conferenceData, or one built from the object when the delivery has none.
OAuth
Fixed
  • We added the missing auth().revoke(), which revokes every access and refresh token of the user through POST /api/oauth/revoke. See Revoke Token.
  • We fixed AuthUrlParams not accepting a theme. AuthUrlParams.builder().theme() now accepts light, dark or auto, which sets the color scheme of the Connect pages.

What's New

Webhook verification

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.

Java 17

The minimum supported Java version is now 17.

SDK
New
  • The SDK now exposes verifyWebhook on webhooks(). It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or throws WebhookVerificationException 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 verifyWebhook.

What's New

Package metadata

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.

SDK
New
  • Package metadata only — 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.

What's New

Webhook subscription management

The SDK now wraps the API’s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.

SDK
New
  • The SDK now exposes subscribeWebhook and unsubscribeWebhook on webhooks, wrapping the API’s POST /subscribe-webhook and POST /unsubscribe-webhook endpoints — previously only reachable with a raw HTTP call.

What's New

Calendar access that was never granted

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.

Unrelated: the event model catches up with three fields it never mapped.

SDK
New
  • The event model now exposes getDescription(), getConferenceData() and getLastModified(). 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.
  • A calendar or event call where no connected account has calendar access now raises CalendarPermissionException, with getAccounts(). It extends AuthenticationException, so existing handlers keep working while new code can read which accounts must reconnect.
  • ConnectedAccount gained getGrantedScopes() and getCalendarPermissionGranted(), so getConnectionStatus reports which connected accounts withheld calendar access and cannot list calendars.

What's New

Localization support

Added an optional lng builder parameter to generateAuthUrl so the Connect authorization pages render in the chosen language (en, es, fr, ar).

SDK
New
  • Added an optional lng builder parameter to generateAuthUrl for localizing the Connect authorization pages (supported: en, es, fr, ar).

What's New

Initial release

Released the initial version of the Java SDK for Mobiscroll Connect. The public surface mirrors the Node SDK reference.

Resources: Auth (OAuth + token refresh), Calendars, and Events.

HTTP stack: OkHttp 4.12 with Jackson 2.18. Requires Java 11+ (CI matrix: 11, 17, 21).

Token-refresh deduplication via AtomicReference<CompletableFuture<TokenResponse>> with CAS-based coordination.

Error hierarchy rooted at MobiscrollConnectException with typed subclasses for authentication, not-found, validation, rate-limit, server, and network failures. HTTP 401 and 403 both surface as AuthenticationException to match Node.

EventListParams.calendarIds is Map<Provider, List<String>>, JSON-encoded in the query string. ConnectionStatus.connections is Map<Provider, List<ConnectedAccount>>. Event CRUD uses singular /event for create/update/delete and plural /events for list.

SDK
New
  • Released the initial version of the Java SDK for Mobiscroll Connect.

Go SDK

What's New

Webhook verification

Deliveries with a meeting on an event now verify.

Missing API features

Revoke, calendar Account and ReadOnly, meeting fields on event writes and the Theme option are now covered.

Events
Fixed
  • We added the missing Account and ReadOnly to Calendar objects. The API returns both for every calendar.
  • We added the missing Conference and ConferenceData to EventCreateData and EventUpdateData. AutoGenerate creates a meeting link.
Webhooks
Fixed
  • We fixed VerifyWebhook rejecting every delivery whose events include a conference, with reason invalid_payload, because a delivery carries conference as an object. Those deliveries now verify: Conference is the join URL of that object, and ConferenceData is the delivery’s conferenceData, or one built from the object when the delivery has none.
OAuth
Fixed
  • We added the missing Auth().Revoke(), which revokes every access and refresh token of the user through POST /api/oauth/revoke. See Revoke Token.
  • We fixed AuthURLParams not accepting a theme. AuthURLParams.Theme now accepts light, dark or auto, which sets the color scheme of the Connect pages.

What's New

Webhook verification

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.

SDK
New
  • The SDK now exposes VerifyWebhook on Webhooks(). It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or a *WebhookVerificationError with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. See VerifyWebhook.

What's New

Package metadata

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.

SDK
New
  • Package metadata only — 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.

What's New

Webhook subscription management

The SDK now wraps the API’s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.

SDK
New
  • The SDK now exposes SubscribeWebhook and UnsubscribeWebhook, wrapping the API’s POST /subscribe-webhook and POST /unsubscribe-webhook endpoints — previously only reachable with a raw HTTP call.

What's New

Calendar access that was never granted

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.

Unrelated: the event model catches up with three fields it never mapped.

SDK
New
  • The event model now exposes Description, ConferenceData and LastModified. 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.
  • A calendar or event call where no connected account has calendar access now raises *CalendarPermissionError, with an Accounts field. It unwraps to *AuthenticationError, so existing handlers keep working while new code can read which accounts must reconnect.
  • ConnectedAccount gained GrantedScopes and CalendarPermissionGranted, so GetConnectionStatus reports which connected accounts withheld calendar access and cannot list calendars.

What's New

Localization support

Added an optional Lng field to AuthURLParams so the Connect authorization pages render in the chosen language (en, es, fr, ar) via GenerateAuthURL.

SDK
New
  • Added an optional Lng field to AuthURLParams for localizing the Connect authorization pages via GenerateAuthURL (supported: en, es, fr, ar).

What's New

Initial release

Released the initial version of the Go SDK for Mobiscroll Connect.

SDK
New
  • Released the initial version of the Go SDK for Mobiscroll Connect.

Ruby SDK

What's New

Event writes

Attendees are sent as email strings, and the API’s own field names are accepted.

Missing API features

Revoke, calendar account and read_only, meeting fields on event writes and the theme option are now covered.

Events
Fixed
  • We added the missing account and read_only to Calendar objects. The API returns both for every calendar.
  • We fixed events.create and events.update leaving out status and conference_data:. They now send status, and conference_data: as conferenceData.
  • We fixed events.create and events.update silently leaving out conferenceData:, allDay:, recurringEventId: and updateMode:, the API’s spelling of conference_data:, all_day:, recurring_event_id: and update_mode:. They now accept both spellings.
  • We fixed events.create and events.update sending attendees as objects. They now send email strings, as the API expects.
  • We fixed events.create and events.update sending color, which the API does not accept on writes.
OAuth
Fixed
  • We added the missing auth.revoke, which revokes every access and refresh token of the user through POST /api/oauth/revoke. See Revoke Token.
  • We fixed generate_auth_url not accepting theme:. It now accepts light, dark or auto, which sets the color scheme of the Connect pages.

What's New

Webhook verification

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.

SDK
New
  • The SDK now exposes verify_webhook on webhooks. It checks that a webhook delivery is signed by Mobiscroll Connect and returns the parsed delivery, or raises WebhookVerificationError with the reason. It fetches the public keys itself and picks up a key rotation without any action from you. See verify_webhook.

What's New

Package metadata

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.

SDK
New
  • Package metadata only — 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.

What's New

Webhook subscription management

The SDK now wraps the API’s webhook subscribe and unsubscribe endpoints, so an integration can register a calendar for delivery or stop it without a raw HTTP call.

SDK
New
  • The SDK now exposes subscribe_webhook and unsubscribe_webhook on webhooks, wrapping the API’s POST /subscribe-webhook and POST /unsubscribe-webhook endpoints — previously only reachable with a raw HTTP call.

What's New

Calendar access that was never granted

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.

SDK
New
  • A calendar or event call where no connected account has calendar access now raises CalendarPermissionError, with an accounts reader. It subclasses AuthenticationError, so existing handlers keep working while new code can read which accounts must reconnect.
  • ConnectedAccount gained granted_scopes and calendar_permission_granted, so get_connection_status reports which connected accounts withheld calendar access and cannot list calendars.

What's New

Localization support

Added an optional lng keyword argument to generate_auth_url so the Connect authorization pages render in the chosen language (en, es, fr, ar).

SDK
New
  • Added an optional lng keyword argument to generate_auth_url for localizing the Connect authorization pages (supported: en, es, fr, ar).

What's New

Initial release

Released the initial version of the Ruby SDK for Mobiscroll Connect.

SDK
New
  • Released the initial version of the Ruby SDK for Mobiscroll Connect.

So what's next?

Follow every Mobiscroll Connect release in your feed reader.

Get updates in RSS feed

Duplicate Session

You have signed in on a different machine. To keep everything in sync, you have been signed out of this session.

If you need to invite team members, manage seats and accounts you can do it from the licenses page.

Duplicate Session

We noticed you are logged in on a different machine and have closed your old session.

If you need to invite team members, manage seats and accounts you can do it from the licenses page.