Webhook data changed, has a bug been introduced?

Description
Today I found out that the data returned by webhook notifications has changed. I have discovered a difference in behavior that I wonder if it is correct or a bug has been introduced. In the case of a webinar the event name inside the RequestBody node shows the prefix “meeting” instead of “webinar”, for example what was previously “webinar.participant_joined” has become “meeting.participant_joined”. This way my application stopped working.
Now I will correct the application to use the event property in the root of the object which continues to be corrected, but is this strange behavior a deliberate modification?

Below an example:

{
applicationId: “xig–KJDRdqPCIjL-cOMUQ”,
monitorTime: 1588076695543,
traceId: “Webhook_68b4ee3d5814484fb768f5d90bd2df67”,
accountId: “5xheyz–RVS9tCjFTFX3ow”,
event: “webinar.participant_joined”, <---- CORRECT
status: “200”,
userId: “9TWiyYXRT1y6XvyTTcYQfg”,
url: “xxxxx/VCSPI/getzoomevent.aspx”,
subscriptionId: “FFx_xtGaSHG1w0sfle0jgw”,
requestHeaders: “N/A”,
requestBody: {
payload: {
account_id: “5xheyz–RVS9tCjFTFX3ow”,
object: {
uuid: “35Ie743qSHaLoYX29vLjFA==”,
participant: {
user_id: “33555456”,
user_name: “DANIELE MANFREDI”,
id: “6uJCMeY0SCazFtS04byc4A”,
join_time: “2020-04-28T12:24:52Z”
},
id: “82022442833”,
type: 5,
topic: “Prova di recupero video produzione”,
host_id: “9TWiyYXRT1y6XvyTTcYQfg”,
duration: 20,
start_time: “2020-04-28T12:20:18Z”,
timezone: “Europe/Rome”
}
},
event: “meeting.participant_joined” <---- NOT CORRECT (BUT IT WAS CORRECT UNTIL SOME TIME AGO)
},
responseHeaders: {
Server: “Microsoft-IIS/8.5”,
Content-Length: “6”,
Date: “Tue, 28 Apr 2020 12:24:56 GMT”,
Content-Type: “text/html; charset=utf-8”
},
runTime: “792”,
ttl: 1590668698,
requestParameters: undefined,
responseData: undefined
}

Error
n/a

Which App Type (OAuth / Chatbot / JWT / Webhook)?
Webhook

Which Endpoint/s?
n/a

How To Reproduce (If applicable)
Join a webinar

Screenshots (If applicable)
n/a

Additional context
n/a

Hey @mustentdev,

That is strange. Are you still continuing to see this issue?

Thanks,
Tommy