Mobiscroll Connect Release API 1.5.3

Announcements
1

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

  • Every calendar returned by GET /calendars now includes account and readOnly, on all four providers.

FIXED

  • With more than one Google account connected, POST, PUT, and DELETE /event against a calendar belonging to any account other than the first returned 400.
  • On iCloud, updating an event previously created through Connect could make it appear as two separate events in the end user’s calendar app.
  • With several accounts connected on one provider, filtering GET /events by calendarIds could return events from every calendar on an account that owned none of the requested ids, instead of returning none.
  • All-day events on iCloud and CalDAV calendars could come back from GET /events dated one day earlier than the calendar shows.
  • On iCloud and CalDAV calendars, GET /events could return link as { params, val } instead of a URL string.

Webhooks

FIXED

  • A webhook subscription could not be created for those same Google calendars, so their changes never reached your webhook.
  • Linking a CalDAV calendar didn’t start webhook delivery on its own — notifications only arrived after separately calling subscribe-webhook. This is now automatic, matching Google, Outlook, and iCloud.
  • Webhook delivery on Google and Outlook calendars could stop silently once a channel expired. Channels are now renewed automatically before that happens.

OAuth

FIXED

  • 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

  • Requests are now limited to 50 per second and 500 per minute, replacing the previous flat limit of 100 per 5 minutes.

MOBISCROLL CONNECT SDKs

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.

Node.js SDK Version 1.5.1

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.

PHP SDK Version 1.5.1

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.

NET SDK Version 1.5.1

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.

Python SDK Version 1.5.1

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.

Java SDK Version 1.5.1

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.

Go SDK Version 1.5.1

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.

Ruby SDK Version 1.5.1

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.

As always, we recommend updating to the latest SDK version for the best experience and newest capabilities.
For release notes please visit our release history