Create Scheduling Configuration Error

Question and Answers
1

I ran into the following error when trying to create a scheduling configuration for a calendar associated with a virtual account:

Endpoint: POST /v3/grants/{grant_id}/scheduling/configurations
Error: Calendar X does not belong to Y

In this case, I had created two virtual accounts with the same email. When I tried to create a scheduling configuration on the calendar associated with the virtual account that was created first I got the error. Creating a scheduling configuration on the second account created with the duplicate email did not cause any error. Is this the expected behavior?

2

I’ve also noticed that if I set up a virtual grant without a valid email, for example I’ve tried using a uuid, then when I go to create a scheduling configuration it gives me the following error: Failed to find a valid Grant for “f38d2bd9-8b01-4973-bbcb-825a2cdece74”

3

Hi @julian in our docs we caution against using emails for virtual accounts. This section also mentions that the email field must be unique. So having two virtual accounts for the same email will cause issues.

Let me investigate and circle back for the second inquiry:

creating virtual account with email field as UUID causes error when creating a scheduler

4

Got it, I must have missed that. But using a non-email account does give me problems with Scheduler API.

5

Hi @julian - I was able to complete the following steps:

  1. Create Virtual Account
  2. Create Virtual Calendar
  3. Create Scheduler Configuration

So to confirm, step 3 is where we are seeing the issue?

I can share the cURL command that I used:

curl --request POST \
  --url "https://api.us.nylas.com/v3/grants/<GRANT_ID>/scheduling/configurations" \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer <API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
    "version": "1.0.0",
    "requires_session_auth": false,
    "participants": [
      {
        "name": "Test",
        "email": "devrel-virtual-calendar",
        "is_organizer": true,
        "availability": {
          "calendar_ids": [
            "primary"
          ]
        },
        "booking": {
          "calendar_id": "primary"
        }
      }
    ],
    "availability": {
      "duration_minutes": 30
    },
    "event_booking": {
      "title": "My test event"
    }
  }'
6

Yes, step 3 is where I’m having the issue. I just tried your cURL command on a grant/calendar I created and got the same error. Could you provide the cURLs you’re using for the first 2 steps just so I can double check on my end? Also is there a chance that the region is causing an issue? I’m on an EU sandbox. That’s the only other thing I noticed that looked different.

7

Sure, here are the steps I used taken from our developer docs:

  1. Create Virtual Calendar Connector and Virtual Account
  2. Create a Virtual Calendar
8

If I use a string like you provided “devrel-virtual-calendar” or “julian-email” for email when creating a virtual calendar then step 3 works. However if I use a uuid for email then I get the error.

9

Yes, there must be something about the implementation that interferes with the logic when email is a UUID. For example, if I set the email to e5dc434b-bcaa-47cb-bb63-d8f4da96b235 then I get the error, but if I do julian@e5dc434b-bcaa-47cb-bb63-d8f4da96b235 then everything works fine.

Not a big deal, I’ll just add a prefix, but odd nonetheless