Skip to content

After rescheduling a booking with a Zoom meeting attachment, videoCallUrl no longer present in API response metadata #7604

@fhinson

Description

@fhinson

Issue Summary

After rescheduling a booking with a Zoom meeting attachment within the cal.com web interface, videoCallUrl no longer present in API response metadata.

Steps to Reproduce

  1. I have an existing booking scheduled in cal.com.
  2. Using the booking API, I'm able to see the videoCallUrl within the metadata response of GET https://api.cal.com/v1/bookings/{id}?apiKey={apiKey}. Response below:
{"attendees": [{"email": "XXX", "locale": "en", "name": "Name", "timeZone": "America/New_York"}], "description": "", "endTime": "2023-03-22T15:30:00.000Z", "eventTypeId": XXXXX, "id": XXXXX, "metadata": {"videoCallUrl": "https://us05web.zoom.us/j/XXXX"}, "startTime": "2023-03-22T15:00:00.000Z", "status": "ACCEPTED", "title": "XXX", "uid": "XXX", "user": {"email": "XXX", "locale": null, "name": "XXX", "timeZone": "Etc/GMT"}, "userId": XXX}
  1. I rescheduled the booking for a different date and time within the web interface at https://app.cal.com/<username>/appointment?rescheduleUid=<uid>.
  2. I made the same GET request as in step 2, but now videoCallUrl no longer present in API response metadata. Response below:
{"attendees": [{"email": "XXX", "locale": "en", "name": "Name", "timeZone": "America/New_York"}], "description": "", "endTime": "2023-03-23T14:30:00.000Z", "eventTypeId": XXXXX, "id": XXXXX, "metadata": {}, "startTime": "2023-03-23T14:00:00.000Z", "status": "ACCEPTED", "title": "XXX", "uid": "XXX", "user": {"email": "XXX", "locale": null, "name": "XXX", "timeZone": "Etc/GMT"}, "userId": XXX}

Technical details

  • Cal.com API Version: v1
  • In the reschedule confirmation email, I was able to access the updated videoCallUrl. However, it is not present in the API response.

Metadata

Metadata

Assignees

Labels

🐛 bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions