Sometimes it's necessary to pass in some custom data when changing the object status. For example, you might need to store the name of the person that booked a seat, to use in the tooltip of a rendered chart.
Extra data is public data
Therefore, you should consider extra data to be public data, and never use it to store information that can identify individual users (names, emails, etc) in clear text. In general, technical identifiers without context are fine, as long as they can't be used to access sensitive data through other parts of your system.
In short: think twice about what you store in extraData :)
/hold take an optional extraData object for each object ID in the request.
extraData must be a JSON object with key value pairs, not a JSON primitive.
- API: added
keepExtraDataflag to calls that change the object status. If set to
true, the existing extra data doesn't get cleared
You can update extra data for objects without changing their status too. Check https://docs.seats.io/docs/api-update-extra-data-for-an-object and https://docs.seats.io/docs/api-update-extra-data-for-multiple-objects for more information.