Supported server-side access to iCloud Calendar for a LINE-based web service

Question

Created 3d

Replies 2

Boosts 0

Participants 2

I am developing a LINE-based service for users in Japan. With each user's explicit consent, our backend would read their selected iCloud calendars and send event reminders through LINE. Users would not be required to install a native iOS or macOS app.

Apple's support article describes Apple Account authorization for supported third-party apps: https://support.apple.com/en-us/121539

Is this authorization available to a web service with this architecture? What are the eligibility requirements, application process, and Calendar integration documentation?
If it is not available, does Apple officially support server-side CalDAV access using a user-generated app-specific password for this use case? What requirements and limitations apply to credential handling, access scope, and synchronization frequency?
Do the requirements differ between reading calendars and potentially creating or updating events in the future? If this architecture is not supported, is there another documented integration path?

I would appreciate links to the relevant documentation or the appropriate technical contact.

Answered by DTS Engineer in 908990022

See this thread.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Answer 1

DTS Engineer OP

Apple

19h

Recommended

See this thread.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Answer 2

LABcare OP

4h

Thank you for pointing us to the iCloud OAuth 2.0 interest form. LABcare is a LINE-based web service, not a native App Store app. With each user’s consent, our server would read their iCloud Calendar to send a summary of the next day’s events via LINE.

Is a web-only service like this eligible to express interest in and obtain this access? The related discussion indicates that an App Store URL is required. Can we provide our web service URL instead, or is there a separate application route for services without an App Store app?

The interest form currently redirects our signed-in account to an unauthorized page. Could you also clarify which Developer Program membership or account role is required to access it, and whether eligibility for this web-only use case can be confirmed before enrollment?