The next batch request receives eventId1, updates eventId2 and creates a new event under the calendar, which is identified using calendarId.
POST /batch HTTP/1.1 Authorization: /*Auth token*/ Host: host Content-Type: multipart/mixed; boundary=batch_foobarbaz Content-Length: total_content_length --batch_foobarbaz Content-Type: application/http Content-ID: <item1: x@barnyard.example.com > GET /calendar/v3/calendars/calendarId/events/eventId1 --batch_foobarbaz Content-Type: application/http Content-ID: <item2: x@barnyard.example.com > PUT /calendar/v3/calendars/calendarId/events/eventId2 Content-Type: application/json Content-Length: part_content_length {{ body }} --batch_foobarbaz Content-Type: application/http Content-ID: <item3: x@barnyard.example.com > POST /calendar/v3/calendars/calendarId/events Content-Type: application/json Content-Length: part_content_length {{ body }} --batch_foobarbaz--
source share