PUT /events Requests Removing `participants` on EWS Accounts

There's know issue when updating events on Exchange Web Services (EWS) accounts using the PUT /events endpoint in the Nylas API. It may have the participants field unintentionally blanked out, but only if you don’t explicitly include it in the update request.

So, even if you’re just changing something simple like the event description, the participant list could be wiped out.

What Accounts Are Affected

This issue is only affecting EWS accounts. Google and Microsoft 365/Outlook accounts are not impacted byt this error.

Google Calendars, anyways, do have a similar issue, only that it's not affecting the participants but theconferencing. You can take the same cautions you take for this case!

What’s the Workaround

Until a permanent fix is implemented, we recommend a quick manual workaround: always include the participants array when sending a PUT /events request to modify an event on an EWS calendar. This ensures the participant list isn’t removed during the update.

Example of the Workaround

To keep things safe and your participant list intact:

1. First, get the full event using a GET /events request.

2. Save the participants array from the response.

3. When crafting your PUT /events request, include both the changes you want to make and the participants field from step 2.

4. Send the request as usual.

Sample PUT Request with Participants Included

curl --location --request PUT 'https://api.us.nylas.com/v3/grants/<grant_id>/events/<event_id>?calendar_id=<calendar_id>' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--data-raw '{
  "description": "Updated description for the event.",
  "participants": [
    {
      "email": "example1@domain.com",
      "name": "Attendee One",
      "status": "noreply"
    },
    {
      "email": "example2@domain.com",
      "name": "Attendee Two",
      "status": "noreply"
    }
  ]
}'

What's Being Done

We’ve already escalated this to our Engineering team and they’re actively working on a permanent fix. Ideally, users shouldn’t have to send unchanged fields just to avoid unexpected deletions, and that’s the goal we’re working toward. We’ll update this article as soon as a fix is released. Thanks for your patience while we work through this. 

Updated May 21, 2025 17:43