In the current API documentation for Meeting Get / Update (but not Create) there is, under settings a key value store property with the field name custom_keys. I am testing its use for storage of an idempotent token to prevent repeat updates.
In testing the Meeting Update API PATCH call accepts this value but Webhook meeting.update triggered does not include it as is documented (which it were). After update calls to GET meeting also do not include set key value pairs for custom_keys against documentation.
Which App Type (OAuth / Chatbot / JWT / Webhook)?
JWT / Webhook
Not sure, perhaps already mentioned above
How To Reproduce (If applicable)
Steps to reproduce the behavior:
Screenshots (If applicable)
If applicable, add screenshots to help explain your problem.
I just saw these updates to the API & wanted to make use of them but there is scant documentation outside of the schema. Is the use of the custom_keys field controlled in some way outside of the API, are there any tests of its use that can be presented as proof?
BTW I would welcome guidance for idempotent update use to prevent repeat calls & potential API rate limiting?