On April 17th to 18th midnight a bunch of new error messages are coming back for a bunch of our customers who are trying to create or update an Engagement through our app through HubSpot API. The error looks like
{ “status” : “error”, “message” : “Property values were not valid: [{\“isValid\”:false,\“message\”:\”\\\“hs_video_conference_url\\\” is a read only property; its value cannot be set.\“,\“error\”:\“READ_ONLY_VALUE\”,\“name\”:\“hs_video_conference_url\”,\“localizedErrorMessage\”:\”\\\“hs_video_conference_url\\\” is a read only property; its value cannot be set.\“,\“propertyValue\”:\”[https://shiphero.zoom.us/j/84123631111\\](https://shiphero.zoom.us/j/84123631111\)“,\“portalId\”:1110269}]”, “category” : “VALIDATION_ERROR”, “errorType” : null, “policyName” : null, “groupName” : null, “type” : “HubspotErrorResponse” }
And it is talking about a field hs_video_conference_url, that is invalid to post but we are not posting it. It is not from our system, so some kind of webhook or something else is adding it. What is interesting that it only appeared at that mentioned date, nothing specifically changed otherwise, these customers were using the same ways to create engagements.
Anyone heard about a change during that time?
Anyone experiencing the same error messages?
Have you looked at the log data in Hubspot? When an API request errors out, you are able to see the payload and response for the failed request. You can check the payload to see if it’s indeed sending that property or not. And also check the headers to see where the request came from.
I checked now the Hubspot log data and there’s no hs_video_conference_url field in the request, or anything like that in the details, so indeed HubSpot is making this up internally somehow.
request body
{
“properties”: {
“hs_meeting_title”: “gworkiMeeting with A 2 B”,
“hubspot_owner_id”: “111110827”,
“hs_meeting_body”: “\n\nIf you need to reschedule, please use the link: [https://fire-abcdefgh.chilipiper.io/reschedule/111111da-768b-4d24-b929-73d111111dbf\\](https://fire-abcdefgh.chilipiper.io/reschedule/111111da-768b-4d24-b929-73d111111dbf\)n\nLaunch Meeting - Zoom”,
“hs_internal_meeting_notes”: null,
“hs_meeting_external_url”:“Launch Meeting - Zoom”,
“hs_meeting_location”: “here: Launch Meeting - Zoom”,
“hs_meeting_start_time”: “2025-04-29T22:00:00Z”,
“hs_meeting_end_time”: “2025-04-29T22:30:00Z”,
“hs_meeting_outcome”: “SCHEDULED”,
“hs_activity_type”: null,
“hs_attachment_ids”: null,
“hs_timestamp”: “2025-04-29T22:00:00Z”
}
}
(response body doesn’t fit)
(I replaced some numbers with random so that i don’t expose data)
Since it is an “hs_” (hubspot created) field, maybe Hubspot was doing something with it or making changes.
I pulled down the schema for the Meetings object (assuming this is object in question) and while the field was created a year ago, I do see that it was UPDATED in March 12, 2025 for my hub. Maybe Hubspot is preparing some updates.
Other than that, no idea!
I’ve just come to add that I am experiencing the same issue. And have confirmed that we are not sending this field in our payload, only `hs_meeting_location`
We are experiencing the same behavior, also not setting the `hs_video_conference_url` field (but we are passing a `hs_meeting_location`).
I implemented a workaround where if i’m trying to send a URL as the `hs_meeting_location` , I don’t and instead send it to `hs_meeting_external_url`. Sending a value that’s not a URL to `hs_meeting_location` seems to still work
I got an answer from HubSpot Customer Support:
“It looks like there was some sort of issue on our end and the team seems to have fixed it.”
So I consider this thread closed/closeable. The issue was on HubSpot side, we came up with the reason, a possible workaround, or many possible workarounds. But that is not needed any more.
Thank you all for your inputs.