Thank you for clarifying, and apologies for any misunderstanding.
At the moment, you’re correct in that when a personal meeting is created using personal meeting ID, a unique meeting ID is also created as seen in the create meeting response. However, in the webhooks it will show your personal meeting ID.
Your suggestion to include a secondary ID along with the personal meeting ID is a great idea, but is not how this currently functions.
I’m happy to raise this internally, as I can definitely appreciate how it would be helpful to have something like a secodary ID in the webhook data. If you’re so inclined, you’re also welcome to suggest this in our #feature-requests channel.
Thanks,
Will