calendar API no longer works after update

[stopwatch9626]

Hi!

I have been able to create events in Synology Calendar via API.
Documentation: https://global.synologydownload.com...r/2.4/enu/Synology_Calendar_API_Guide_enu.pdf

Since the synology calendar update to version 2.5.0-21145, I get the error code 9009
Unfortunately the developer documentation is not up to date.Any ideas?

I can access events from the calendar, but cant create (after update)

 

[Superjunky]

I am dealing with the same issue.
Did you get it solved? If so, would you post an update here?

I did a bunch of debugging, up to a point where it all seems a shot in the dark.
Unfortunately Synology-Support is not helpful either.

 

[Superjunky]

Some more info on the error codes for the Synology Calendar API:

{
    "9001":"error:exceed_attach_quota",
    "9002":"error:exceed_event_quota",
    "9003":"error:copy_to_sub_event_failed",
    "9004":"error:update_newer_version_event",
    "9005":"error:update_non_existent_event",
    "9006":"error:database_operation_failed",
    "9007":"error:no_permission",
    "9008":"error:daemon_connnect_failed",
    "9009":"error:invalid_parameter",
    "9010":"error:apply_setting_failed",
    "9011":"error:default_fail_handler",
    "9012":"error:edit_event_failed",
    "9013":"error:socket_connect_failed",
    "9014":"error:invalid_ics_data",
    "9015":"error:version_mismatch",
    "9016":"error:deprecate_api",
    "9017":"error:fake_email_converting",
    "9018":"error:email_is_duplicated",
    "9019":"error:team_contact_upgrading",
    "9020":"error:fake_email_update_failed",
    "9021":"error:repeated_event_boundary_backfilling",
    "9022":"error:repeated_event_boundary_backfill_failed"
}

 

[Superjunky]

I found the required parameters. Take a special note of the last two, they need a value with at least an empty array [ ].
And dtstart and dtend now need a timestamp.

api: SYNO.Cal.Event
method: create
version: 5
cal_id: "/SomeUser/sdfghjkl/"
original_cal_id: "/SomeUser/sdfghjkl/"
summary: "test"
is_all_day: false
tz_id: "Europe/Amsterdam"
dtstart: 1715583600
dtend: 1715587200
is_repeat_evt: false
color: ""
description: ""
participant: []
notify_setting: []

 

[Telos]

Calendar issues reported recently by Community users...

I suggest you open a support ticket.

 

[Superjunky]

Calendar issues reported recently by Community users...

I suggest you open a support ticket.

This was no bug, just a lack of documentation.

 

[sh4rxy]

With the new parameters and dtstart and dtend as timestamp it works fine. But with the method „set“ always the error 9009 comes up. Any ideas ?

 

[Superjunky]

Yes I figured it out.

For set you'll need at least the parameters below.
It's required to add the current dav_etag, which you first must retrieve via get.

api: SYNO.Cal.Event
method: set
version: 5
evt_id: 102293
cal_id: "/User/xntphmr/"
original_cal_id: "/User/xntphmr/"
summary: "Some summary"
color: ""
description: ""
dav_etag: "aqveyjqyewhpecenzujahpjipqcjvhqr"
is_all_day: false
tz_id: "Europe/Amsterdam"
dtstart: 1716188400
dtend: 1716192000
is_repeat_evt: false
repeat_setting: null
participant: []
notify_setting: []
location_info: {"address":"","gps":{"lat":-1,"lng":-1},"map_type":"","name":"","place_id":""}
attachments: []

The trick is to inspect your browser's network traffic while using the Calendar-browser-app (Synology Calendar GUI).