How do you manage API changes to avoid breaking consumers?

To manage API changes and prevent breaking consumers, I apply the following approaches:

• API Versioning. Introducing new versions while maintaining old ones so clients can migrate gradually.
• Backward Compatibility. Adding new fields or endpoints without removing or changing existing ones.
• Deprecation with Notification. Informing consumers about planned deprecation of features with sufficient lead time.
• Documentation and Communication. Providing detailed descriptions of changes and informing all stakeholders.
• Testing and Monitoring. Checking compatibility and tracking errors after release.

For example, if you need to add a new field to a JSON response, it's better to make it optional so that old clients continue to work without changes.