Type changes: target_access_levels, id, and email_header_and_footer_enabled fields
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
Three field types were corrected in the OpenAPI spec, which may break clients that assumed the old types:
target_access_levelsinAPI_Entities_BroadcastMessagechanged fromtype: string→type: array(of integers); clients parsing this as a string will break.idin bothAPI_Entities_ApplicationWithSecretandAPI_Entities_Applicationchanged fromtype: string→type: integer; clients treating applicationidas a string may break.email_header_and_footer_enabledinAPI_Entities_Appearancechanged fromtype: string→type: boolean; clients treating this as a string may break.
The remaining changes are purely additive: format: date-time annotations and example values were added to several fields with no type or behaviour change.